libtool-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU Libtool 2.2.7b released (2.2.8 release candidate).


From: Ralf Wildenhues
Subject: Re: GNU Libtool 2.2.7b released (2.2.8 release candidate).
Date: Sat, 22 May 2010 11:04:57 +0200
User-agent: Mutt/1.5.20 (2009-10-28)

[ moving from libtool@ ]

Hi Gary,

* Gary V. Vaughan wrote on Fri, May 21, 2010 at 02:22:09AM CEST:
> The Libtool Team is pleased to announce release candidate 2.2.7b of GNU
> Libtool.  If there are no serious deficiencies reported in this release,
> it will be renumbered as 2.2.8 and re-released (otherwise, we'll fix
> any problems and put out 2.2.7d first).

Thank you for cutting the alpha release, and fixing the issues you found
along the way.

As a veeery minor nit may I note that with git, it is common to separate
the first line of the commit entry from the rest, in order for 'git log
--oneline' to work as expected.  I'm not sure whether they relaxed that,
because I would have expected the shortlog mail for v2.2.7b to contain
long log lines because of that missing empty line.  Anyway, much talk,
little problem.  (Yes, the ChangeLog style is rather the other way, with
no empty lines within one commit entry; I use a short editor macro to
convert between them ...)

When writing a release announcement, I usually forget to set reply-to or
mail-f'up-to.  I know that it is a contentious topic whether to use one
or the other, and there are lots of reasons both ways (reply-to
shouldn't go to list here to facilitate security responses to author
only, mail-f'up-to isn't honored by many MUA's etc.), but still, would
you guys be ok with the following patch?  Having replies go to announce
lists seems wrong and unnecessary.

Thanks,
Ralf

   * HACKING: Set Reply-To: in announcement emails.

diff --git a/HACKING b/HACKING
index cbd3cfd..bea81fe 100644
--- a/HACKING
+++ b/HACKING
@@ -756,6 +756,7 @@ or obtained by writing to the Free Software Foundation, 
Inc.,
 ===============================
 
 To: address@hidden, address@hidden
+Reply-To: address@hidden
 Subject: GNU Libtool @VERSION@ released (alpha release).
 
 The Libtool Team is pleased to announce alpha release @VERSION@ of GNU
@@ -831,6 +832,7 @@ The README file explains how to capture the verbose test 
output.
 
 To: address@hidden
 Cc: address@hidden, address@hidden
+Reply-To: address@hidden
 Subject: GNU Libtool @VERSION@ released.
 
 The Libtool Team is pleased to announce the release of GNU Libtool



reply via email to

[Prev in Thread] Current Thread [Next in Thread]