From: Eric Sunshine <sunshine@sunshineco.com>
To: "Øyvind A. Holm" <sunny@sunbase.org>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH] git-notes.txt: Explain how to transfer notes between repos
Date: Wed, 10 Sep 2014 15:59:00 -0400 [thread overview]
Message-ID: <CAPig+cQeJz2DZ+=qdAM-grOC=kQ+DSTL8gsycyq8djrGoaPVJg@mail.gmail.com> (raw)
In-Reply-To: <1410357414-691-1-git-send-email-sunny@sunbase.org>
On Wed, Sep 10, 2014 at 9:56 AM, Øyvind A. Holm <sunny@sunbase.org> wrote:
> The documentation for git notes did not mention anywhere how to transfer
> notes between repositories, create a section that explains this topic.
>
> Signed-off-by: Øyvind A. Holm <sunny@sunbase.org>
> ---
> diff --git a/Documentation/git-notes.txt b/Documentation/git-notes.txt
> index 310f0a5..4237bec 100644
> --- a/Documentation/git-notes.txt
> +++ b/Documentation/git-notes.txt
> @@ -264,6 +264,45 @@ prior to the merge, these will also be removed by this notes merge
> strategy.
>
>
> +TRANSFERRING NOTES ACROSS REPOSITORIES
> +--------------------------------------
> +
> +Notes are not transferred by default when using the standard
> +fetch/push commands, but has be done explicitly. To fetch all notes
At minimum: s/has be/has to be/
Slightly improved phrasing, perhaps:
Notes are not transferred, by default, when using the standard
fetch/push commands, thus must be transferred explicitly.
> +from a particular remote, use
s/use/use:/
> +------------
> +$ git fetch origin refs/notes/*:refs/notes/*
> +------------
> +
> +`git fetch` can be configured to automatically fetch notes from a
> +remote with this command:
> +
> +------------
> +$ git config --add remote.origin.fetch +refs/notes/*:refs/notes/*
> +------------
> +
> +To transfer notes to a remote repository:
> +
> +------------
> +$ git push origin refs/notes/*
> +------------
> +
> +If you don't want to fetch or push all notes stored under
> +`refs/notes/`, replace the asterisk with the specific type of notes
> +you want to transfer:
> +
> +------------
> +$ git fetch origin refs/notes/commits:refs/notes/commits
> +------------
> +
> +or
> +
> +------------
> +$ git push origin refs/notes/commits
> +------------
> +
> +
> EXAMPLES
> --------
>
> --
> 2.1.0.127.g0c72b98
next prev parent reply other threads:[~2014-09-10 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 13:56 [PATCH] git-notes.txt: Explain how to transfer notes between repos Øyvind A. Holm
2014-09-10 19:59 ` Eric Sunshine [this message]
2014-09-10 23:31 ` Johan Herland
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPig+cQeJz2DZ+=qdAM-grOC=kQ+DSTL8gsycyq8djrGoaPVJg@mail.gmail.com' \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=sunny@sunbase.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).