git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir Panteleev" <thecybershadow@gmail.com>
To: git@vger.kernel.org
Subject: Re: Commit annotations (editable commit messages)
Date: Sat, 13 Feb 2010 01:18:26 +0200	[thread overview]
Message-ID: <op.u71e00v4m02fvl@cybershadow.mshome.net> (raw)
In-Reply-To: 32541b131002121455s46bfe15aie484e9be484259c6@mail.gmail.com

On Sat, 13 Feb 2010 00:55:46 +0200, Avery Pennarun <apenwarr@gmail.com>  
wrote:

> 2010/2/12 Vladimir Panteleev <thecybershadow@gmail.com>:
>> You have to agree, being able to edit commit messages in a controlled
>> (logged/versioned) fashion is pretty useful. Aside mundane corrections  
>> such
>> as typos or undocumented changes, it makes it possible to document bugs  
>> and
>> other unintended changes in the commit that they were introduced. This  
>> is
>> possible in centralized VCSes and is implemented in Subversion  
>> (controlled
>> by a server-side hook).
>
> 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
>
> Have fun,
>
> Avery

Wow, thanks! Looks like I'm behind the times. (Currently stuck with  
msysGit/1.6.5)

The documentation looks pretty scant. Does anyone know how close were my  
suggestions to the actual implemented behavior (esp. regarding rebasing)?

-- 
Best regards,
  Vladimir                            mailto:thecybershadow@gmail.com

  reply	other threads:[~2010-02-12 23:19 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 [this message]
2010-02-13  1:01     ` Mark Lodato
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=op.u71e00v4m02fvl@cybershadow.mshome.net \
    --to=thecybershadow@gmail.com \
    --cc=git@vger.kernel.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.
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).