[Pharo-dev] Unambiguously differentiating official and local builds [Was [Vm-dev] Moving the Cog subversion repository to githup at 2016-6-16 7am UTC]

Serge Stinckwich serge.stinckwich at gmail.com
Thu Jun 16 18:32:19 EDT 2016

On Thu, Jun 16, 2016 at 11:08 PM, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> Hi Alistair,
> On Thu, Jun 16, 2016 at 1:43 PM, Alistair Grant <akgrant0710 at gmail.com>
> 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
Every DSL ends up being Smalltalk

More information about the Pharo-dev mailing list