From: Mark Lodato <lodatom@gmail.com>
To: Vladimir Panteleev <thecybershadow@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Commit annotations (editable commit messages)
Date: Fri, 12 Feb 2010 20:01:00 -0500 [thread overview]
Message-ID: <ca433831002121701u7c4e47ddn2f8bc19c45b2bd03@mail.gmail.com> (raw)
In-Reply-To: <op.u71e00v4m02fvl@cybershadow.mshome.net>
2010/2/12 Vladimir Panteleev <thecybershadow@gmail.com>:
>> It sounds like you want to read about a new feature called git-notes:
>> http://www.kernel.org/pub/software/scm/git/docs/git-notes.html
>
> Wow, thanks! Looks like I'm behind the times. (Currently stuck with
> msysGit/1.6.5)
Yes, what you described sounds *exactly* like git-notes :)
> The documentation looks pretty scant. Does anyone know how close were my
> suggestions to the actual implemented behavior (esp. regarding rebasing)?
1, 2, 3, and 4 are all implemented, as far as I know. However, I
don't think notes copy during a rebase. My gut feeling is that you
probably shouldn't be rebasing so much that this is an issue. I'm
guessing that you should copy the note to the new commit ID after the
rebase.
I have also found the documentation lacking. It helped a bit to see
the history. It's pretty compact in the logs. Here are two commands
to isolate the commits:
git log --reverse fed8a7de3592~..df27f6280545
gitk fed8a7de3592..df27f6280545
--
Mark
next prev parent reply other threads:[~2010-02-13 1:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 22:32 Commit annotations (editable commit messages) Vladimir Panteleev
2010-02-12 22:55 ` Avery Pennarun
2010-02-12 23:18 ` Vladimir Panteleev
2010-02-13 1:01 ` Mark Lodato [this message]
2010-02-13 21:46 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ca433831002121701u7c4e47ddn2f8bc19c45b2bd03@mail.gmail.com \
--to=lodatom@gmail.com \
--cc=git@vger.kernel.org \
--cc=thecybershadow@gmail.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).