From: Michael J Gruber <git@drmicha.warpmail.net>
To: Christian MICHON <christian.michon@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: on pulling/cloning git notes
Date: Thu, 24 Jun 2010 11:48:21 +0200 [thread overview]
Message-ID: <4C2329E5.8050904@drmicha.warpmail.net> (raw)
In-Reply-To: <AANLkTilDMVU6b7SwHx0Bztu1rTCubiIPTuDDX6pJBcHx@mail.gmail.com>
Christian MICHON venit, vidit, dixit 24.06.2010 10:22:
> Hi list,
>
> I've been playing recently with git notes and figured out how to push
> my notes to my central gitolite server, tweaking .git/config in this
> way (adding a push section):
>
> [remote "gitolite"]
> url = gitolite:daat
> fetch = +refs/heads/*:refs/remotes/gitolite/*
> push = +refs/notes/*:refs/notes/*
>
> When trying to to a 'git clone --mirror' from that same gitolite
> server, I was expecting to get back refs/notes, but I did not.
>
> Did I miss something or git notes are actually not meant to be cloned/pulled?
>
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.
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.
Michael
next prev parent reply other threads:[~2010-06-24 9:49 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 [this message]
2010-06-24 12:25 ` Christian MICHON
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=4C2329E5.8050904@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=christian.michon@gmail.com \
--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).