From: Sebastian Schuberth <sschuberth@gmail.com>
To: Jeff King <peff@peff.net>
Cc: larsxschneider@gmail.com, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH v2] config: add '--sources' option to print the source of a config value
Date: Wed, 10 Feb 2016 16:33:11 +0100 [thread overview]
Message-ID: <CAHGBnuMMN_xEVDJ_dqWgL6QCGK08hy=ggg=6PzkSCinHr=QeFg@mail.gmail.com> (raw)
In-Reply-To: <20160210125429.GA8078@sigill.intra.peff.net>
On Wed, Feb 10, 2016 at 1:54 PM, Jeff King <peff@peff.net> wrote:
>> +--sources::
>> + Augment the output of all queried config options with the
>> + source type (file, stdin, blob, cmd) and the actual source
>> + (config file path, ref, or blob id if applicable).
>
> I think something like "cmdline" might be more descriptive than "cmd".
I agree "cmdline" is better than "cmd".
> So the format here is like:
>
> file\t<filename>\t<value...>
> blob\t<blob>\t<value...>
> stdin\t\t<value...>
> cmd\t\t<value...>
>
> where two of the prefixes have nothing in the second slot. I expected
> something more like:
>
> file:<filename>\t</value...>
> blob:<blob>\t<value...>
> stdin\t<value...>
> cmd\t<value...>
>
> with a single delimited slot for the source, which can then be broken
> down further if desired. I can't think of any reason to prefer one over
> the other rather than personal preference, though. They can both be
> parsed unambiguously.
I also would have expected sopme like the latter, except that I'd also
expect a colon after "stdin" and "cmd" (or "cmdline", as said above).
I.e. the colon should be part of the prefix to mark it as such.
--
Sebastian Schuberth
next prev parent reply other threads:[~2016-02-10 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 10:13 [PATCH v2] config: add '--sources' option to print the source of a config value larsxschneider
2016-02-10 12:47 ` Ramsay Jones
2016-02-10 15:28 ` Sebastian Schuberth
2016-02-10 16:03 ` Ramsay Jones
2016-02-10 12:54 ` Jeff King
2016-02-10 15:33 ` Sebastian Schuberth [this message]
2016-02-10 15:40 ` Jeff King
2016-02-10 15:57 ` Sebastian Schuberth
2016-02-10 16:24 ` Jeff King
2016-02-10 19:03 ` Eric Sunshine
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='CAHGBnuMMN_xEVDJ_dqWgL6QCGK08hy=ggg=6PzkSCinHr=QeFg@mail.gmail.com' \
--to=sschuberth@gmail.com \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--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).