[git-users] Re: Extend .gitignore to support setting of a file size limit so that all files over a certain size will by automatically ignored
On Thursday, May 7, 2015 at 10:45:29 PM UTC+2, Roger Mendes wrote: Allow .gitignore to support setting a file size limit so that all files over a certain size will by automatically ignored when performing git add, commit -a...; Small note, there is no parameter to git-commit that will automatically add all untracked files. Exclusions to this size limit for files can be allowed by specifying exceptions '!' syntax that already exists. It probably should be considered to have a default limit already built into git of say 100MB (used by github) which can be changed in the .gitignore file. This would avoid accidental commits of large files which are known to be poorly supported. This seems like a fairly simple feature to add, I'm not sure why no one has done this or thought of it given the number of complaints, questions... with large file handling. We can ignore by file name attribute, why not by file size? Yes, I know I can add pre-commit scripts... to workaround this issue, but there should be a better way (or maybe I'm missing something?). The use-case is somewhat exotic. I think most people do some fair share of thinking before tracking new files, and the mental cost of manually leaving out or ignoring large files is not that high. If you do set some arbitrary limit on what constitutes a large file which should not be tracked, you're trying to automate something which is not so easy to automate. I mean, 5 years from now, storage (SSD), network-speed and memory will be a lot cheaper, and Git will make many performance enhancements, so maybe by then it will perfectly OK to check in 100 MB files, or even GB files. You'd have to review and maintain these .gitignore size entries regularly. If you still can justify why this would be a valuable feature for a noteworthy amount of Git users, the place to suggest new features is the main Git mailing list: https://gist.github.com/tfnico/4441562 -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Extend .gitignore to support setting of a file size limit so that all files over a certain size will by automatically ignored
On Thu, 7 May 2015 13:45:29 -0700 (PDT) Roger Mendes sprog...@gmail.com wrote: [...] This seems like a fairly simple feature to add, I'm not sure why no one has done this or thought of it given the number of complaints, questions... with large file handling. We can ignore by file name attribute, why not by file size? Yes, I know I can add pre-commit scripts... to workaround this issue, but there should be a better way (or maybe I'm missing something?). I humbly think this proposition is ill-concieved in fact. The problem you're trying to solve using technical tools is, in fact, social / political: if people are unable/unwilling to properly review what they commit, they have to be educated, and then possibly penalized on repeated faults. I can understand why github has this setting in place: they provide free hosting for hundreds of thousand throwaway repositories, and obviously have to combat goofs like accidentially committing junk. In real environments, like private / corporate repos, such goofs are way easier to fix: you just tell the person to amend a commit and force-push, or let a user with more rights do that, if required, while explaining why things gone bad and how to avoid that in the future. IOW, it's possible to provide an educational hands-holding in such a case. On the other hand, ignoring files by name is useful for everyone as the most common application of a VCS is managing the source code of a program, and so you want to ignore backup files made by text editor, IDE- or toolchain-generated crap, binary files which are the result of compiling the source code etc. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[git-users] Re: Extend .gitignore to support setting of a file size limit so that all files over a certain size will by automatically ignored
On Friday, May 8, 2015 at 2:15:29 AM UTC+5:30, Roger Mendes wrote: Allow .gitignore to support setting a file size limit so that all files over a certain size will by automatically ignored when performing git add, commit -a...; Exclusions to this size limit for files can be allowed by specifying exceptions '!' syntax that already exists. It probably should be considered to have a default limit already built into git of say 100MB (used by github) which can be changed in the .gitignore file. This would avoid accidental commits of large files which are known to be poorly supported. Well IMHO you can always use some script such as find . -size +10M .gitignore Also have you heard of this extension https://git-lfs.github.com/ I would suggest this if you are in need to use the binary files too This seems like a fairly simple feature to add, I'm not sure why no one has done this or thought of it given the number of complaints, questions... with large file handling. We can ignore by file name attribute, why not by file size? Yes, I know I can add pre-commit scripts... to workaround this issue, but there should be a better way (or maybe I'm missing something?). -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[git-users] Offering bounty: Help me use git5 to keep GitHub / Piper in sync
Hi git folk, I will award a peer bonus to anyone who shows me how to solve this scenario with specific commands. I'd like to open source a site that has a piper-dependency for it's publishing. There are two nodes in the system: 1. GitHub.com -- where users can submit changes to us 2. Piper -- the source of truth. Changes come from GitHub dirty (not Googler-reviewed) and are merged into Piper (presumably via git5) on a per-change basis, giving us a chance to review what's coming in on either Gerrit or Critique. I need the commands for these six things: 1. Setting up a local environment that has the proper mirroring scheme 2. How to push changes that originated in Piper up to GitHub 3. Conflict resolution workflow in cases where both GitHub and Piper have changed 4. How to pull changes from GitHub into Piper (creating a CL or Gerrit change each time that gets Googler-approved before submission) 5. Conflict resolution workflow in cases where both GitHub and Perforce have changed 6. Destroying a local environment that is no longer needed (presumably you can just delete the directory) I'd prefer that this be done with git5 mirror so that it's fast, and to be CITC-compatible so changes can be tweaked in Cider if desired. Any help at all appreciated, but the person who offers specific commands will get the bonus (and the thanks of the Cloud Platform team). -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
