From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH] add: make "add -u/-A" update full tree without pathspec (step 3)
Date: Wed, 23 Mar 2011 21:02:46 +0700 [thread overview]
Message-ID: <AANLkTikBQg_pT2NX9vQc+DcB+4HA35VXBpQyRtAU_ewG@mail.gmail.com> (raw)
In-Reply-To: <7v1v1yifc9.fsf_-_@alter.siamese.dyndns.org>
2011/3/23 Junio C Hamano <gitster@pobox.com>:
> Now long after 1.8.0 happened, people should have got used to the
> new default behaviour and it is no longer necessary to give the
> migration advice anymore.
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
>
> * And this concludes the two-year long series from the future ;-)
Beautiful.
I'd expect you kill add.treewideupdate too. Say one year after this
patch, we can start to annoy users asking them to remove
add.treewideupdate and switch to new behavior. Another year goes by,
we refuse to work with those who still keep add.treewideupdate config.
A consistent default behavior is a good thing. If I help a git user
and later realize "git add -u" on their machine does not work as I
expect it to be, it'd be less pleasant.
--
Duy
next prev parent reply other threads:[~2011-03-23 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 19:49 What's cooking in git.git (Mar 2011, #02; Sun, 20) Junio C Hamano
2011-03-20 20:43 ` Jens Lehmann
2011-03-20 21:06 ` Junio C Hamano
2011-03-20 21:22 ` Junio C Hamano
2011-03-20 21:36 ` Matthieu Moy
2011-03-21 0:06 ` Junio C Hamano
2011-03-21 11:16 ` Jeff King
2011-03-21 14:28 ` Junio C Hamano
2011-03-23 0:02 ` [PATCH] add: make "add -u/-A" update full tree without pathspec Junio C Hamano
2011-03-23 5:17 ` [PATCH] add: make "add -u/-A" update full tree without pathspec (step 2) Junio C Hamano
2011-03-23 5:19 ` [PATCH] add: make "add -u/-A" update full tree without pathspec (step 3) Junio C Hamano
2011-03-23 14:02 ` Nguyen Thai Ngoc Duy [this message]
2011-03-23 15:54 ` Junio C Hamano
2011-03-22 10:57 ` What's cooking in git.git (Mar 2011, #02; Sun, 20) Ævar Arnfjörð Bjarmason
2011-03-22 18:00 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikBQg_pT2NX9vQc+DcB+4HA35VXBpQyRtAU_ewG@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).