[Top][All Lists]

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

Re: info locate has repeated paragraph

From: James Youngman
Subject: Re: info locate has repeated paragraph
Date: Sat, 23 Aug 2014 12:07:48 +0100

I don't think we should worry about "correcting" git log entries prior
to 2009 when generating ChangeLog.

For your (I hope) convenience I just pushed a change which splits the
1987-2008 ChangeLog entries out into a separate file, ChangeLog-2008.
The naming follows the convention used in coreutils.   We can leave
that file as-is, and concentrate on just generating the ChangeLog

If you need help with anything to do with this, or if you have
questions, please just let me know.


On Thu, Aug 21, 2014 at 6:39 AM, Bernhard Voelker
<address@hidden> wrote:
> On 08/19/2014 09:25 AM, James Youngman wrote:
>> Bernhard,
>> Thanks for the patch.   I added a ChangeLog entry (which findutils
>> still maintains "manually"[*]), applied and pushed it as
>> 68e2b1d6fd420787903142c02ce1a5e3ea2a7754.   Thanks again for your
>> contributions to findutils.
> thanks, I forgot that (again).
>> [*] There is actually IMO no reason to continue to maintain ChangeLog
>> manually, we should be able to generate the ChangeLog file from git
>> commit messages (at least those more recent than the start of Jan
>> 2008) with some small automated edits (typo fixes, etc).   Other GNU
>> projects already do this, and so we should be able just to use the
>> infrastructure they built for this.
> Okay, I'm working on it.  The generation part is easy, but adding
> the fixing rules in a build-aux/git-fix-log file is a bit more work
> to get the same result (until 2008).
> Thanks & have a nice day,
> Berny

This email is intended solely for the use of its addressee, sender,
and any readers of a mailing list archive in which it happens to
appear.   If you have received this email in error, please say or type
three times, "I believe in the utility of email disclaimers," and then
reply to the author correcting any spellings (and, optionally, any
incorrect spellings), accompanying these with humorous jests about the
author's parentage.   If you are not the addressee, you are
nevertheless permitted to both copy and forward this email since
without such permissions email systems are unable to transmit email to
anybody, intended recipient or not.  To those still reading by this
point, the author would like to apologise for being unable to maintain
a consistent level of humour throughout this disclaimer.  Contents may
settle during transit.  Do not feed the animals.

reply via email to

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