Skip to content

commands: make 4gb smudge warning show on all platforms #2507

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 15, 2017

Conversation

ttaylorr
Copy link
Contributor

This pull request teaches the git-lfs-smudge(1) and git-lfs-filter-process(1) commands to display the 4gb object warning on all platforms, not just runtime.GOOS == "windows".

In situations where multiple collaborators are working on a repository among different operating systems, it is useful for a contributor running macOS to know that he/she/they can potentially cause an issue for another collaborator running Windows when they commit a file larger than 4gb.


/cc @git-lfs/core
/cc #2459

@ttaylorr ttaylorr added this to the v2.3.0 milestone Aug 14, 2017
@ttaylorr ttaylorr requested a review from technoweenie August 14, 2017 16:48
Copy link
Contributor

@technoweenie technoweenie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think including the warning when adding files would be good too. We can allow the commit, but I think it'd be better to warn them sooner (before push) rather than later (during fetch/clone).

What do you think?

@ttaylorr
Copy link
Contributor Author

What do you think?

That sounds like a great idea. I have a patch ready, but I'd rather put it in a separate PR so it makes it easier to generate the changelog. I gave this a shot in: #2510.

@ttaylorr ttaylorr merged commit 9022e8e into master Aug 15, 2017
@ttaylorr ttaylorr deleted the large-warning-all-platforms branch August 15, 2017 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants