Re: [PATCH v3] build: add default aliases
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Oct 1, 2013, 01:12 UTC
- Message-ID
- <CACsJy8De8uER-=N4DonycE9i0cOG-mvcx+bRnQ=Gxt4X9_1TfQ@mail.gmail.com>
- In-Reply-To
- <20130930193343.GW9464@google.com>
On Tue, Oct 1, 2013 at 2:33 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 9 quoted lines
> Michael Haggerty wrote: > >> That being said, independent of aliases, there are many other config >> settings that can affect commands that might be used in documentation or >> scripts, and which also could be the source of errors for the non-vigilent. > > Yep, this is a problem, too (I'm looking at you, "git push"). We try > to avoid this problem or balance it against convenience by being > careful when adding new configuration, but sometimes we slip up.
I think the problem is we start pushing too much on the porcelain front and forget about plumbing. "git push" is for human, but I don't think there's an equivalent for scripts. "git branch --list" vs "git for-each-ref" is a good example.
-- Duy