From: Christian MICHON <christian.michon@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git list <git@vger.kernel.org>
Subject: Re: on pulling/cloning git notes
Date: Thu, 24 Jun 2010 14:25:13 +0200 [thread overview]
Message-ID: <AANLkTilGS6t29J4NQMgseZY9WD1kAPCr9oFeQt1RaWjP@mail.gmail.com> (raw)
In-Reply-To: <4C2329E5.8050904@drmicha.warpmail.net>
On Thu, Jun 24, 2010 at 11:48 AM, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
> As you can see from the default "fetch" line above, "refs/heads" are
> fetched by default (when cloning, fetching etc.), but nothing else
> (well, besides some tags). You can set up an additional fetch refspec to
> get the notes also.
I'm actually doing a fresh clone elsewhere, using 'git clone --mirror
gitolite:daat'.
I was expecting to grab everything from the remote refs, as in this
case my .git/config will look like this:
[remote "origin"]
fetch = +refs/*:refs/*
mirror = true
url = gitolite:daat
> It's not done by default because it's up to you decide what to do with
> the notes. Sometimes, you want them to end up in "refs/notes" so that
> they are displayed by default. But maybe you want them in
> "refs/notes/remotes/gitolites" e.g. and display them only on request
> (--show-notes=remotes/gitolite), or merge them into your own notes.
>
So the * in .git/config was misleading me. Instead I changed the fetch
to this after the original clone, then performed an incremental fetch
and it worked.
[remote "origin"]
fetch = +refs/heads/*:refs/notes/*
mirror = true
url = gitolite:daat
Thanks for the hint, Michael!
--
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !
next prev parent reply other threads:[~2010-06-24 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 8:22 on pulling/cloning git notes Christian MICHON
2010-06-24 9:48 ` Michael J Gruber
2010-06-24 12:25 ` Christian MICHON [this message]
2010-06-24 13:16 ` Michael J Gruber
2010-06-24 13:27 ` Christian MICHON
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTilGS6t29J4NQMgseZY9WD1kAPCr9oFeQt1RaWjP@mail.gmail.com \
--to=christian.michon@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).