From: Thomas Rast <trast@student.ethz.ch>
Date: Sun, 04 Sep 2011 18:43:00 GMT
Subject: Re: Lost association between TAGS and COMMITs when rebased a git(1) repository
Message-ID: <201109042043.01159.trast@student.ethz.ch>
In-Reply-To: <CABNEGjyXLnSvjhBewNDsjW=rthRh0HY+KgC05vPNPu5QCaAgXQ@mail.gmail.com>

Tor Arntsen wrote:
> On Sun, Sep 4, 2011 at 4:30 PM, knittl <knittl89@googlemail.com> wrote:
> >
> > On Sun, Sep 4, 2011 at 3:32 AM, John S. Urban <urbanjost@comcast.net> wrote:
> > > With my first use of git(1) I  created a small project with about 200
> > > "commits".  When this was complete, I needed to label each commit with
> > > information pointing it to a section of a document. I used tags for this.
> >
> > Use git notes[1] to attach additional info to existing commits. Git
> > notes will by default be copied when using git rebase or git commit
> > --amend (cf. notes.rewrite.<command> config)
> 
> Is that true? I've always lost the notes when rebasing. I just tried
> that again now (1.7.5.4), and after a rebase the notes attached to any
> commit that was rebased just disappeared. I've always had to hunt down
> and re-create the notes. It would indeed be much more convenient if
> the notes would tag along.

Yes, that support has been present since 1.7.1, but it's not enabled
by default: you need to configure notes.rewriteRef.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch