From: David Bremner <david@tethera.net>
To: "W. Trevor King" <wking@tremily.us>, notmuch <notmuch@notmuchmail.org>
Subject: Re: [PATCH v2] nmbug: Add 'clone' and replace FETCH_HEAD with @{upstream}
Date: Sun, 06 Apr 2014 09:27:59 -0300 [thread overview]
Message-ID: <87d2gu4p80.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <de7dd9d4021cd17350df4423bc13f3da35f2b324.1394410765.git.wking@tremily.us>
"W. Trevor King" <wking@tremily.us> writes:
> With two branches getting fetched (master and config), the branch
> referenced by FETCH_HEAD is ambiguous. For example, I have:
>
> $ cat FETCH_HEAD
> 41d7bfa7184cc93c9dac139d1674e9530799e3b0 \
> not-for-merge branch 'config' of http://nmbug.tethera.net/git/nmbug-tags
> acd379ccb973c45713eee9db177efc530f921954 \
> not-for-merge branch 'master' of http://nmbug.tethera.net/git/nmbug-tags
This patch seems OK. I think it makes sense to have an "nmbug clone"
command; perhaps the implementation can be simplified in the future (or
perhaps not).
d
next prev parent reply other threads:[~2014-04-06 12:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 0:28 [PATCH v2] nmbug: Add 'clone' and replace FETCH_HEAD with @{upstream} W. Trevor King
2014-04-06 12:27 ` David Bremner [this message]
2014-04-08 11:11 ` WARNING: backwards incompatible change to nmbug pushed David Bremner
2014-04-08 15:57 ` [PATCH] NEWS: Document the recent 'nmbug clone' and @{upstream} changes W. Trevor King
2014-04-09 11:22 ` David Bremner
2014-04-09 21:01 ` W. Trevor King
2014-04-10 1:01 ` David Bremner
2014-04-10 2:05 ` W. Trevor King
2014-04-08 11:12 ` [PATCH v2] nmbug: Add 'clone' and replace FETCH_HEAD with @{upstream} David Bremner
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=87d2gu4p80.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).