From: Duy Nguyen <pclouds@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
Felipe Contreras <felipe.contreras@gmail.com>,
Jeff King <peff@peff.net>, Git Mailing List <git@vger.kernel.org>,
David Aguilar <davvid@gmail.com>
Subject: Re: [PATCH v3] build: add default aliases
Date: Tue, 1 Oct 2013 08:12:37 +0700 [thread overview]
Message-ID: <CACsJy8De8uER-=N4DonycE9i0cOG-mvcx+bRnQ=Gxt4X9_1TfQ@mail.gmail.com> (raw)
In-Reply-To: <20130930193343.GW9464@google.com>
On Tue, Oct 1, 2013 at 2:33 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> 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
next prev parent reply other threads:[~2013-10-01 1:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-21 19:20 [PATCH v3] build: add default aliases Felipe Contreras
2013-09-24 4:53 ` Jeff King
2013-09-24 5:32 ` Felipe Contreras
2013-09-24 5:37 ` Jeff King
2013-09-24 5:49 ` Felipe Contreras
2013-09-24 6:18 ` Jeff King
2013-09-24 6:41 ` Felipe Contreras
2013-09-24 6:46 ` Jeff King
2013-09-24 6:59 ` Felipe Contreras
2013-09-24 18:39 ` Jonathan Nieder
2013-09-24 19:30 ` John Szakmeister
2013-09-28 22:41 ` Felipe Contreras
2013-09-29 3:18 ` Michael Haggerty
2013-09-29 3:37 ` Felipe Contreras
2013-09-30 19:33 ` Jonathan Nieder
2013-10-01 1:12 ` Duy Nguyen [this message]
2013-10-15 22:34 ` Junio C Hamano
2013-10-16 3:43 ` Felipe Contreras
2013-10-17 19:51 ` Junio C Hamano
2013-10-17 21:34 ` Felipe Contreras
2013-09-24 9:19 ` John Szakmeister
2013-09-24 10:25 ` Felipe Contreras
2013-09-24 11:06 ` John Szakmeister
2013-09-24 14:35 ` Felipe Contreras
2013-09-25 13:33 ` John Szakmeister
2013-09-25 14:29 ` Felipe Contreras
2013-09-25 14:55 ` Matthieu Moy
2013-09-25 15:08 ` Felipe Contreras
2013-09-25 15:13 ` Matthieu Moy
2013-09-25 15:16 ` Felipe Contreras
2013-09-25 16:05 ` Matthieu Moy
2013-09-25 16:36 ` Felipe Contreras
2013-09-24 15:21 ` SZEDER Gábor
2013-09-24 15:33 ` [PATCH v4] " Felipe Contreras
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACsJy8De8uER-=N4DonycE9i0cOG-mvcx+bRnQ=Gxt4X9_1TfQ@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=davvid@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=mhagger@alum.mit.edu \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).