On 17 June 2016 at 00:08, Eliot Miranda <[email protected]> wrote:
> What I don't understand is how, or indeed why, one stages modified files. > I get that adding files requires informing git. But why doesn't "git > commit" commit modified files by default? Why do I have to use git commit > -a to include modified files? > The mindset with git is that your working copy is a sort of experimentation area where you can have a crazy scientist attitude. When you commit, however, you switch hats and become the thorough developer that cares about your future self, and therefore has done all changes in a perfect didactic sequence so that you can understand what the hell your future-past-self was doing. If your crazy-scientist-self is already auto-censored into producing limpid incremental patches, then he can use git aliases for his preferred workflow (for instance I have git ci, git co, git st configured to mimic their svn counterparts; git staged shows a diff of what's to be committed next, etc) -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet
