Re: [PATCH 1.8.0] add: make "add -u" update full tree without pathspec
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Mar 1, 2011, 11:22 UTC
- Message-ID
- <AANLkTimRuUdGsgkt63PspvNXXjusZeOJWMhSXQ5nS81t@mail.gmail.com>
- In-Reply-To
- <7vk4gkk5pd.fsf@alter.siamese.dyndns.org>
On Mon, Feb 28, 2011 at 1:56 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Perhaps the migration plan is not helpful enough? If that is the case we > would need to rethink it to be even less impactful.
But how many people may be impacted this way? If it's few, probably not worth the headaches. I want to believe the number is few, but I think anybody who ssh to some machine may have the same problem because they may not control what's in that machine.
I can only think of another way, ugly though: add a new command name, say "nad", that goes with new behavior, "add" remains old school. This way if I mistakenly type 'nad' on unsupported git, it refuses and I'm safe. Whether the new name is temporary (until the behavior flip in "add") or permanent is another ugly matter to think about.
Or accept that evolution is painful and go with current plan, which I'm OK too.
-- Duy