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.