From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 7/8] remote-bzr: reorganize the way 'wanted' works
Date: Tue, 28 May 2013 21:31:07 -0500 [thread overview]
Message-ID: <51a5686ba7f2c_807b33e189951a@nysa.mail> (raw)
In-Reply-To: <7vvc632g1s.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> wrote:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
> > + wanted = get_config('remote-bzr.branches').rstrip().split(', ')
>
> Two minor nits and one design suggestion:
>
> - Why rstrip() not strip()?
The purpose of the strip is to remove the _single_ "\n" at the end that
subprocess communicate. Maybe get_config() should do that.
> It appears that this only is helping
> an end-user "mistake" like this:
>
> git config remote-bzr.branches 'trunk, devel, test '
>
> without helping people who have done this:
>
> git config remote-bzr.branches 'trunk, devel, test'
No, that's tnot it.
> - Is
>
> git config remote-bzr.branches trunk,devel,test
>
> a grave sin?
>
> In other words, wouldn't we want something like this instead?
>
> map(lambda s: s.strip(), get_config('...').split(','))
Yeah, that might make sense.
> - Doesn't allowing multi-valued variable, e.g.
>
> [remote-bzr]
> branches = trunk
> branches = devel
> branches = test
>
> make it easier for the user to manage this configuration by
> e.g. selectively removing or adding tracked branches?
How would the 'git config' command look like?
Either way, that's orthogonal to this patch.
--
Felipe Contreras
next prev parent reply other threads:[~2013-05-29 2:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 2:24 [PATCH v2 0/8] remote-bzr: patches for next Felipe Contreras
2013-05-25 2:24 ` [PATCH v2 1/8] remote-bzr: recover from failed clones Felipe Contreras
2013-05-25 2:24 ` [PATCH v2 2/8] remote-bzr: fix for files with spaces Felipe Contreras
2013-05-25 2:24 ` [PATCH v2 3/8] remote-bzr: simplify get_remote_branch() Felipe Contreras
2013-05-25 2:24 ` [PATCH v2 4/8] remote-bzr: delay cloning/pulling Felipe Contreras
2013-05-25 2:24 ` [PATCH v2 5/8] remote-bzr: change global repo Felipe Contreras
2013-05-25 2:24 ` [PATCH v2 6/8] remote-bzr: trivial cleanups Felipe Contreras
2013-05-25 2:24 ` [PATCH v2 7/8] remote-bzr: reorganize the way 'wanted' works Felipe Contreras
2013-05-28 17:02 ` Junio C Hamano
2013-05-29 2:31 ` Felipe Contreras [this message]
2013-05-29 16:42 ` Junio C Hamano
2013-05-29 17:03 ` Felipe Contreras
2013-05-25 2:24 ` [PATCH v2 8/8] remote-bzr: add fallback check for a partial clone 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51a5686ba7f2c_807b33e189951a@nysa.mail \
--to=felipe.contreras@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 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 NNTP newsgroup(s).