From: Thomas Rast <trast@student.ethz.ch>
To: Tor Arntsen <tor@spacetec.no>
Cc: knittl <knittl89@googlemail.com>,
"John S. Urban" <urbanjost@comcast.net>, <git@vger.kernel.org>
Subject: Re: Lost association between TAGS and COMMITs when rebased a git(1) repository
Date: Sun, 4 Sep 2011 20:43:00 +0200 [thread overview]
Message-ID: <201109042043.01159.trast@student.ethz.ch> (raw)
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
next prev parent reply other threads:[~2011-09-04 18:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 1:32 Lost association between TAGS and COMMITs when rebased a git(1) repository John S. Urban
2011-09-04 10:02 ` PJ Weisberg
2011-09-04 13:40 ` Michael Witten
2011-09-04 14:03 ` Michael Witten
[not found] ` <CA+sFfMcMgPDyCi6SCS=Sc4XFrug_Ee7vbmBBkmkwfwwpXg8yCg@mail.gmail.com>
2011-09-04 14:38 ` Michael Witten
2011-09-04 17:20 ` Philip Oakley
2011-09-04 18:15 ` knittl
2011-09-04 14:30 ` knittl
2011-09-04 14:43 ` Michael Witten
2011-09-04 15:39 ` Jakub Narebski
2011-09-04 18:16 ` Tor Arntsen
2011-09-04 18:43 ` Thomas Rast [this message]
2011-09-04 19:11 ` Tor Arntsen
2011-09-04 20:18 ` John S. Urban
2011-09-04 20:28 ` [PATCH] Documentation: "on for all" configuration of notes.rewriteRef Thomas Rast
2011-09-04 20:43 ` Tor Arntsen
2011-09-07 21:23 ` Jeff King
2011-09-07 21:29 ` Thomas Rast
2011-09-07 21:35 ` Jeff King
[not found] ` <CACx-yZ1Ce3x=ZSdm5iY3JqYjVGVs5uPnb12-tMJP7zWsGuMK_Q@mail.gmail.com>
2011-09-04 16:40 ` Lost association between TAGS and COMMITs when rebased a git(1) repository John S. Urban
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=201109042043.01159.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=knittl89@googlemail.com \
--cc=tor@spacetec.no \
--cc=urbanjost@comcast.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.