From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Christian Couder <christian.couder@gmail.com>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Arjun Sreedharan <arjun024@gmail.com>,
Philip Oakley <philipoakley@iee.org>, Git <git@vger.kernel.org>
Subject: Re: [PATCH] introduce git root
Date: Tue, 02 Dec 2014 09:26:00 -0800 [thread overview]
Message-ID: <xmqqd282m09j.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20141202070415.GC1948@peff.net> (Jeff King's message of "Tue, 2 Dec 2014 02:04:15 -0500")
Jeff King <peff@peff.net> writes:
> There is also "git var", which is a catch-all for printing some deduced
> environmental defaults. I'd be just as happy to see it go away, though.
> Having:
>
> git --exec-path
> git --toplevel
> git --author-ident
>
> all work would make sense to me (I often get confused between "git
> --foo" and "git rev-parse --foo" when trying to get the exec-path and
> git-dir). And I don't think it's too late to move in this direction.
> We'd have to keep the old interfaces around, of course, but it would
> immediately improve discoverability and consistency.
Yeah, I too think the above makes sense. I forgot about "var", but
it should go at the same time we move kitchen-sink options out of
"rev-parse". One less command to worry about at the UI level means
you do not have to say "if you want to learn about X, ask 'var', if
you want to learn about Y, ask 'rev-parse', use 'git' itself for Z".
next prev parent reply other threads:[~2014-12-02 17:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 20:00 [PATCH] introduce git root Arjun Sreedharan
2014-11-29 23:08 ` Philip Oakley
2014-11-30 4:35 ` Arjun Sreedharan
2014-11-30 11:58 ` Matthieu Moy
2014-12-01 3:04 ` Junio C Hamano
2014-12-01 4:17 ` Christian Couder
2014-12-01 4:53 ` Junio C Hamano
2014-12-02 7:04 ` Jeff King
2014-12-02 10:05 ` Christian Couder
2014-12-02 17:26 ` Junio C Hamano [this message]
2014-12-04 9:22 ` Jeff King
2014-12-04 19:02 ` Junio C Hamano
2014-12-04 20:00 ` Matthieu Moy
2014-12-04 20:19 ` Junio C Hamano
2014-12-04 21:12 ` Jeff King
2014-12-04 21:30 ` Junio C Hamano
2014-12-05 2:27 ` Christian Couder
2014-12-05 9:27 ` Jeff King
2014-12-07 5:23 ` Christian Couder
2014-12-09 18:17 ` Junio C Hamano
2014-12-10 9:16 ` Christian Couder
2014-12-10 20:10 ` Jeff King
2014-12-10 21:08 ` 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=xmqqd282m09j.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=arjun024@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=philipoakley@iee.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.