Re: What's cooking in git.git (Apr 2013, #05; Mon, 15)
- From
Jeff King <peff@peff.net>
- Date
- Apr 18, 2013, 21:44 UTC
- Message-ID
- <20130418214427.GA10119@sigill.intra.peff.net>
- In-Reply-To
- <7vvc7j4j0u.fsf@alter.siamese.dyndns.org>
On Thu, Apr 18, 2013 at 02:37:53PM -0700, Junio C Hamano wrote:
Show 17 quoted lines
> Because this is to help people who are _used_ to seeing "git add" > not take the removals into account, I doubt that "Did I want those > updated or not? Let me see the details of them." will be the > question they will be asking [*1*]. > > I dunno. > > > [Footnote] > > *1* "I know I didn't want to include these removals to the index, > but I learned today that in later Git I should make myself more > clear if I want to keep doing so; thanks for letting me know.", or > "I've long been assuming that I have to say 'git add' and 'git rm' > separately, but I learned today that I can say 'add --all', and in > later Git I do not even have to; thanks for letting me know." are > the two reactions I expected.
I am expecting a reaction more like "Hmm, I never thought about it before. Does that make sense to me or not? Let me think about which paths it pertains to and decide".
Which I admit is no more likely than the scenarios you outlined, but it is close to what I thought the first time I saw the warning.
-Peff