From: Frank Terbeck <ft@bewatermyfriend.org>
To: zsh-workers@zsh.org
Subject: Re: Next release
Date: Sat, 10 Dec 2011 20:55:23 +0100 [thread overview]
Message-ID: <8739csxkus.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <20111210194648.2ce77de2@pws-pc.ntlworld.com> (Peter Stephenson's message of "Sat, 10 Dec 2011 19:46:48 +0000")
Peter Stephenson wrote:
> I think when we can get to the point where I can type
> "Util/changelog.sh", or whatever, and recreate the ChangeLog since the
> last release, or the release label/change specified as an argument, I
> will be entirely happy. However, that's a prerequisite, rather than a
> reason, for abandoning it.
That should not be a problem. And obviously, if you'd still like to keep
a manual ChangeLog after all, I won't complain. That way I'll get to try
that merge-driver. ;)
Regards, Frank
next prev parent reply other threads:[~2011-12-10 20:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 14:11 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 [this message]
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 ` ChangeLog generation Frank Terbeck
2012-01-24 19:40 ` ChangeLog generation (was: Re: Next release) Bart Schaefer
2012-01-25 0:59 ` ChangeLog generation Frank Terbeck
2011-12-09 23:38 ` Next release Phil Pennock
-- strict thread matches above, loose matches on Subject: below --
1998-10-26 9:59 next release Zefram
1998-10-26 10:17 ` Peter Stephenson
1998-10-27 16:15 ` Geoff Wing
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=8739csxkus.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).