From: David Bremner <david@tethera.net>
To: "W. Trevor King" <wking@tremily.us>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH 2/2] nmbug-status: Use 'show-ref --heads' for loading configs
Date: Mon, 14 Jul 2014 06:51:22 -0300 [thread overview]
Message-ID: <87pph8b751.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <20140713181339.GB23983@odin.tremily.us>
"W. Trevor King" <wking@tremily.us> writes:
> On Sun, Jul 13, 2014 at 09:30:56AM -0300, David Bremner wrote:
>> I consider it a useful feature that it works without the user
>> configuring a local branch. I agree that in more complex setups
>> this ambiguity is not as nice, but I'd rather it was only the
>> minority of users with unusual setups (e.g. multiple remotes) have
>> to do configuration.
>
> I could work up a patch that tried ‘git show-ref -s config’ first, and
> only fell back to ‘show-ref -s --heads’ if there were multiple
> matches. That way folks with only origin/config wouldn't need a local
> branch, but folks with multiple config-carrying remotes (or a single
> config-carrying remote and a local branch) would have to have a local
> config to break the tie. That's possible, and not *too* complicated,
> but I personally prefer the consistency of just requiring a local
> config branch.
It might be simpler to implement (and understand) to try first the local
config branch and then fall back to "origin/config".
d
next prev parent reply other threads:[~2014-07-14 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 19:16 [PATCH 0/2] nmbug-config errors for illegible configs W. Trevor King
2014-05-10 19:16 ` [PATCH 1/2] nmbug-status: Clarify " W. Trevor King
2014-07-13 12:28 ` David Bremner
2015-03-15 8:32 ` David Bremner
2015-03-15 9:34 ` W. Trevor King
2014-05-10 19:16 ` [PATCH 2/2] nmbug-status: Use 'show-ref --heads' for loading configs W. Trevor King
2014-07-13 12:30 ` David Bremner
2014-07-13 18:13 ` W. Trevor King
2014-07-14 9:51 ` David Bremner [this message]
2014-07-14 17:52 ` W. Trevor King
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: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pph8b751.fsf@maritornes.cs.unb.ca \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=wking@tremily.us \
/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://yhetil.org/notmuch.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).