Re: [PATCH 1/2] commit-template: remove outdated notice about explicit paths

Kaartic Sivaraam writes: > It just recently dawned on me that the message, > > Explicit paths specified without -i or -o; assuming --only paths.. > > is translated and "git grep" shows it's presence in the files present > in the 'po' directory. What should be

Re: [PATCH 1/2] commit-template: remove outdated notice about explicit paths

On Fri, 2017-06-30 at 17:42 +0530, Kaartic Sivaraam wrote: > The notice that "git commit " default to "git commit > --only " was there since 756e3ee0 ("Merge branch > 'jc/commit'", 2006-02-14).  Back then, existing users of Git > expected the command doing "git commit --include ", and > after the

[PATCH 1/2] commit-template: remove outdated notice about explicit paths

The notice that "git commit " default to "git commit --only " was there since 756e3ee0 ("Merge branch 'jc/commit'", 2006-02-14). Back then, existing users of Git expected the command doing "git commit --include ", and after the behaviour of the command was changed to align with other people's

Re: [PATCH 1/2] commit-template: remove outdated notice about explicit paths

On Thu, 2017-06-29 at 10:56 -0700, Junio C Hamano wrote: > When I said "I would have ... if I were doing this", I merely meant > exactly that---as I weren't doing it, I left it up to you.  But you > did it the way anyways, which is very nice of you ;-). > It made a *lot* of sense, that's why. :)

Re: [PATCH 1/2] commit-template: remove outdated notice about explicit paths

Kaartic Sivaraam writes: > The notice that "git commit " default to "git commit > --only " was there since 756e3ee0 ("Merge branch > 'jc/commit'", 2006-02-14). Back then, existing users of Git > expected the command doing "git commit --include ", and > after we

[PATCH 1/2] commit-template: remove outdated notice about explicit paths

The notice that "git commit " default to "git commit --only " was there since 756e3ee0 ("Merge branch 'jc/commit'", 2006-02-14). Back then, existing users of Git expected the command doing "git commit --include ", and after we changed the behaviour of the command to align with other people's