From: "W. Trevor King" <wking@tremily.us>
To: Michal Sojka <sojkam1@fel.cvut.cz>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH v3] nmbug: Add an 'init' command
Date: Sat, 29 Nov 2014 12:18:29 -0800 [thread overview]
Message-ID: <20141129201829.GI4062@odin.tremily.us> (raw)
In-Reply-To: <20141129200917.GH4062@odin.tremily.us>
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
On Sat, Nov 29, 2014 at 12:09:17PM -0800, W. Trevor King wrote:
> On Sat, Nov 29, 2014 at 10:40:01AM +0100, Michal Sojka wrote:
> > On Út, říj 28 2014, W. Trevor King wrote:
> > > + _spawn(
> > > + args=['git', 'init', '--separate-git-dir', NMBGIT, workdir],
> > > + wait=True)
> > > + _git(args=['config', '--unset', 'core.worktree'], wait=True)
> > > + _git(args=['config', 'core.bare', 'true'], wait=True)
> >
> > Why do you create a non-bare repository and then make it bare?
>
> Bare repositories don't usually have upstream tracking branches. See
> the commit message for c2001674 (nmbug: Add 'clone' and replace
> FETCH_HEAD with @{upstream}, 2014-03-09) for details [1]. I can
> resubmit this patch with a commit message that mentions the
> explanation in c2001674 if folks want the extra clarity here.
Ah, it seems that the lack of remote-tracking branches is unique to
'clone --bare'. When I compare 'init --bare' with the above (using
Git 2.1.0), the only difference in the resulting repository is that
the the 'init --bare' form doesn't set core.logallrefupdates, while
the form above sets core.logallrefupdates to true. I'll submit v4
using 'init --bare' and an explicit core.logallrefupdates config.
Cheers,
Trevor
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-11-29 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 21:39 [PATCH v3] nmbug: Add an 'init' command W. Trevor King
2014-11-29 9:40 ` Michal Sojka
2014-11-29 20:09 ` W. Trevor King
2014-11-29 20:18 ` W. Trevor King [this message]
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=20141129201829.GI4062@odin.tremily.us \
--to=wking@tremily.us \
--cc=notmuch@notmuchmail.org \
--cc=sojkam1@fel.cvut.cz \
/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).