git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Herland <johan@herland.net>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
	"Daniel Nyström" <daniel.nystrom@timeterminal.se>
Subject: Re: [Q] Mark files for later commit?
Date: Tue, 29 Mar 2011 09:38:41 +0200	[thread overview]
Message-ID: <201103290938.41528.johan@herland.net> (raw)
In-Reply-To: <4D91858F.7030404@drmicha.warpmail.net>

On Tuesday 29 March 2011, Michael J Gruber wrote:
> Note that you can share
> notes when you set up refspecs etc in a push/pull based workflow. (I'm
> not sure how well we support merging/pulling notes refs yet.)

Since v1.7.4, you can use "git notes merge" for merging notes ref. It's not 
yet integrated with "pull", though, so typically you want to fetch it to a 
different ref name, and then manually "git notes merge" that into the 
original notes ref.

E.g. if you want to sync "refs/notes/foo" with remote "bob", you can "git 
fetch bob refs/notes/foo:refs/notes/bobs_foo", and then
merge them with "git notes --ref=foo merge bobs_foo".

> This does not work well in a patch/e-mail-based workflow.

...although there have been mailing list discussions on getting notes added 
to "git format-patch" output (after the "---"), and then picked up again by 
"git am".


...Johan

-- 
Johan Herland, <johan@herland.net>
www.herland.net

  reply	other threads:[~2011-03-29  7:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29  6:04 [Q] Mark files for later commit? Daniel Nyström
2011-03-29  6:49 ` Junio C Hamano
2011-03-29  7:09   ` Michael J Gruber
2011-03-29  7:38     ` Johan Herland [this message]
2011-03-29  7:45       ` Michael J Gruber
2011-03-29  7:51   ` Junio C Hamano
2011-03-29  9:18     ` Daniel Nyström
2011-03-29 12:01       ` Michael J Gruber
2011-03-29 12:15         ` Daniel Nyström

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=201103290938.41528.johan@herland.net \
    --to=johan@herland.net \
    --cc=daniel.nystrom@timeterminal.se \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).