W. Trevor King wk...@tremily.us writes:
I think doing a fetch immediately after a clone deserves a comment.
I commented in the commit message. Basically everything from “One
tricky bit is that bare repositories don't set upstream tracking
branches by default” down through “gives us the
"W. Trevor King" 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
On Sat, Mar 08, 2014 at 08:26:33AM -0800, W. Trevor King wrote:
> That's going to create ~/.nmbug/.git though, if we want to preserve
> the current bare-style ~/.nmbug/ layout, we'd need something like:
>
> $ TEMPDIR=$(mktemp -d)
> $ git clone --no-checkout --separate-git-dir=~/.nmbug \
> >
On Sat, Mar 08, 2014 at 08:43:26AM -0400, David Bremner wrote:
> W. Trevor King 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
W. Trevor King wk...@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
On Sat, Mar 08, 2014 at 08:43:26AM -0400, David Bremner wrote:
W. Trevor King 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',
On Sat, Mar 08, 2014 at 08:26:33AM -0800, W. Trevor King wrote:
That's going to create ~/.nmbug/.git though, if we want to preserve
the current bare-style ~/.nmbug/ layout, we'd need something like:
$ TEMPDIR=$(mktemp -d)
$ git clone --no-checkout --separate-git-dir=~/.nmbug \
From: "W. Trevor King"
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
From: W. Trevor King wk...@tremily.us
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