From: Frank Terbeck <ft@bewatermyfriend.org>
To: zsh-workers@zsh.org
Subject: Re: ChangeLog generation
Date: Wed, 25 Jan 2012 01:26:49 +0100 [thread overview]
Message-ID: <8739b4hbjq.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <20120124190616.44ae8cc0@pws-pc.ntlworld.com> (Peter Stephenson's message of "Tue, 24 Jan 2012 19:06:16 +0000")
Peter Stephenson wrote:
[...]
> We still need some way of associating the mailing list posting with the
> change set, which is a bit of a puzzle since you are likely to commit it
> to your local repository first. It doesn't need to be in comments (I
> couldn't see any way of updating them when pushing), it could be in some
> other metadata, so there may well be some workaround. We're sunk
> without it, though, since tracing changes back to the discussion about
> it on the mailing list is crucial for working out the intention behind
> changes.
[...]
This sounds like a job for `git-notes'¹², which is additional data you
can stick to an object (like a commit) without changing the object
itself (leaving the hash-sums of the history intact).
My experience with them is limited, but that shouldn't be the biggest
problem. ;)
Regards, Frank
¹ <http://schacon.github.com/git/git-notes.html>
² <http://progit.org/2010/08/25/notes.html>
next prev parent reply other threads:[~2012-01-25 0:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 14:11 Next release Peter Stephenson
2011-12-09 16:37 ` Bart Schaefer
2011-12-09 16:42 ` Peter Stephenson
2011-12-12 16:28 ` _arguments and state_descr (Re: Next release) Bart Schaefer
2011-12-12 16:46 ` Peter Stephenson
2011-12-12 18:15 ` Bart Schaefer
2011-12-09 19:50 ` Next release Frank Terbeck
2011-12-10 17:19 ` Peter Stephenson
2011-12-10 19:20 ` Frank Terbeck
2011-12-10 19:46 ` Peter Stephenson
2011-12-10 19:55 ` Frank Terbeck
2012-01-24 13:03 ` ChangeLog generation (was: Re: Next release) Frank Terbeck
2012-01-24 19:06 ` Peter Stephenson
2012-01-25 0:26 ` Frank Terbeck [this message]
2012-01-24 19:40 ` Bart Schaefer
2012-01-25 0:59 ` ChangeLog generation Frank Terbeck
2011-12-09 23:38 ` Next release Phil Pennock
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=8739b4hbjq.fsf@ft.bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).