From: Junio C Hamano <gitster@pobox•com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
Cc: Jeff King <peff@peff•net>,
Christian Couder <christian.couder@gmail•com>,
Arjun Sreedharan <arjun024@gmail•com>,
Philip Oakley <philipoakley@iee•org>, Git <git@vger•kernel.org>
Subject: Re: [PATCH] introduce git root
Date: Thu, 04 Dec 2014 12:19:53 -0800 [thread overview]
Message-ID: <xmqqr3wfrwuu.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <vpqegsfchi4.fsf@anie.imag.fr> (Matthieu Moy's message of "Thu, 04 Dec 2014 21:00:35 +0100")
Matthieu Moy <Matthieu.Moy@grenoble-inp•fr> writes:
> Junio C Hamano <gitster@pobox•com> writes:
>
>> Jeff King <peff@peff•net> writes:
>>
>>> Christian raised the issue of cluttering the "git --option"
>>> namespace,
>>> and I do agree that's a potential issue.
>>
>> I am not sure if that is an issue at all. You will need the same
>> number of options to cover all the necessary "computables" somewhere
>> anyway.
>>
>> "git --show-this-or-that-computable" is not more or not less
>> cluttering compared to "git var --show-this-or-that-computable".
>
> I disagree.
>
> Right now, a user reading "man git" sees --version, --help, -C,
> --exec-path, --html-path, --man-path, ... at a flat list (it's actually
> the first thing he can read from the man page).
Ahh, OK, you are worried about these "--give-me-computed-values"
mixed with other kinds of options. I didn't consider that part of
the equation.
OK, "git var --exec-path" (and --friends), that is.
next prev parent reply other threads:[~2014-12-04 20:20 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
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 [this message]
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=xmqqr3wfrwuu.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=Matthieu.Moy@grenoble-inp$(echo .)fr \
--cc=arjun024@gmail$(echo .)com \
--cc=christian.couder@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=peff@peff$(echo .)net \
--cc=philipoakley@iee$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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