On Thu, Jun 16, 2016 at 11:08 PM, Eliot Miranda <[email protected]> wrote: > Hi Alistair, > > On Thu, Jun 16, 2016 at 1:43 PM, Alistair Grant <[email protected]> > wrote: >> >> On Thu, Jun 16, 2016 at 01:07:23PM -0700, Eliot Miranda wrote: >> > Hi All, >> > >> > so after fixing "git remote get-url origin" to fail over to "git remote >> > show origin | filter and munge" the culture shock of "git commit -a" >> > (git >> > commit does nothing ?!?!?) >> >> "git commit" will commit anything that has been "git add"ed to the >> index. -a is a convenience to automatically stage files that have been >> modified. > > > 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?
Because you can choose what files will be part of the commit (cherry-picking changes). -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/
