All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
	Git List <git@vger.kernel.org>
Subject: Re: Review of git multimail
Date: Wed, 03 Jul 2013 10:02:34 +0200	[thread overview]
Message-ID: <51D3DA9A.9090604@alum.mit.edu> (raw)
In-Reply-To: <7vsizwiowt.fsf@alter.siamese.dyndns.org>

On 07/03/2013 12:21 AM, Junio C Hamano wrote:
> Ramkumar Ramachandra <artagnon@gmail.com> writes:
> 
>>>     def get(self, name, default=''):
>>>         try:
>>>             values = self._split(read_git_output(
>>>                     ['config', '--get', '--null', '%s.%s' % (self.section, name)],
>>>                     env=self.env, keepends=True,
>>>                     ))
>>
>> Wait, what is the point of using --null and then splitting by hand
>> using a poorly-defined static method?  Why not drop the --null and
>> splitlines() as usual?
> 
> You may actually have spotted a bug or misuse of "--get" here.
> 
> With this sample configuration:
> 
>         $ cat >sample <<\EOF
>         [a]
>                 one = value
>                 one = another
> 
>         [b]
>                 one = "value\nanother"
>         EOF
> 
> A script cannot differentiate between them without using '--null'.
> 
> 	$ git config -f sample --get-all a.one
>         $ git config -f sample --get-all b.one
> 
> But that matters only when you use "--get-all", not "--get".  If
> this method wants to make sure that the user did not misuse a.one
> as a multi-valued configuration variable, use of "--null --get-all"
> followed by checking how many items the command gives you back would
> be a way to do so.

No, the code in question was a simple sanity check (i.e., mostly a check
of my own sanity and understanding of "git config" behavior) preceding
the information-losing next line "return values[0]".  If it had been
meant as a check that the user hadn't misconfigured the system, then I
wouldn't have used assert but rather raised a ConfigurationException
with an explanatory message.

I would be happy to add the checking that you described, but I didn't
have the impression that it is the usual convention.  Does code that
wants a single value from the config usually verify that there is
one-and-only-one value, or does it typically just do the equivalent of
"git config --get" and use the returned (effectively the last) value?

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/

  reply	other threads:[~2013-07-03  8:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 19:23 Review of git multimail Ramkumar Ramachandra
2013-07-02 20:51 ` John Keeping
2013-07-02 21:34   ` Ramkumar Ramachandra
2013-07-02 22:21 ` Junio C Hamano
2013-07-03  8:02   ` Michael Haggerty [this message]
2013-07-03  8:16     ` Junio C Hamano
2013-07-03  8:29     ` John Keeping
2013-07-03  8:33       ` John Keeping
2013-07-03  0:10 ` Michael Haggerty
2013-07-03 10:23   ` Ramkumar Ramachandra
2013-07-03 11:02     ` Ramkumar Ramachandra
2013-07-03 11:41     ` Michael Haggerty
2013-07-03 21:09     ` Jed Brown
2013-07-04  8:11       ` Matthieu Moy
2013-07-04  8:27       ` Michael Haggerty

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=51D3DA9A.9090604@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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.