From: David Bremner <david@tethera.net>
To: "W. Trevor King" <wking@tremily.us>, notmuch@notmuchmail.org
Subject: Re: [PATCH] nmbug: Add 'clone' and replace FETCH_HEAD with @{upstream}
Date: Sat, 08 Mar 2014 08:43:26 -0400 [thread overview]
Message-ID: <87siqsrhch.fsf@zancas.localnet> (raw)
In-Reply-To: <80db13662a0313711ca3a91e338a63d35e64a83c.1391898002.git.wking@tremily.us>
"W. Trevor King" <wking@tremily.us> writes:
> +sub do_clone {
> + my $repository = shift;
> + system ('git', 'clone', '--bare', $repository, $NMBGIT) == 0
> + or die "'git clone' exited with nonzero value\n";
> + my $branch = git ('symbolic-ref', 'HEAD');
> + $branch =~ s|^refs/heads/||;
> + git ('config', 'remote.origin.fetch', '+refs/heads/*:refs/remotes/origin/*');
> + git ('config', "branch.$branch.remote", 'origin');
> + git ('config', "branch.$branch.merge", 'refs/heads/$branch');
> + do_fetch();
> +}
I think doing a fetch immediately after a clone deserves a comment.
>
> @@ -473,7 +487,7 @@ sub diff_index {
> sub diff_refs {
> my $filter = shift;
> my $ref1 = shift || 'HEAD';
> - my $ref2 = shift || 'FETCH_HEAD';
> + my $ref2 = shift || '@{upstream}';
I wonder about hard-coding '@{upstream}' in several places. What do you
think about a global "constant"? OF course it was hard-coded FETCH_HEAD
before, but I think not in quite as many places.
next prev parent reply other threads:[~2014-03-08 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 22:21 [PATCH] nmbug: Add 'clone' and replace FETCH_HEAD with @{upstream} W. Trevor King
2014-03-08 12:43 ` David Bremner [this message]
2014-03-08 16:26 ` W. Trevor King
2014-03-08 16:30 ` W. Trevor King
2014-03-09 16:35 ` 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=87siqsrhch.fsf@zancas.localnet \
--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).