[Top][All Lists]

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

Re: [PATCH 0/8] maintenance patches

From: Bernhard Voelker
Subject: Re: [PATCH 0/8] maintenance patches
Date: Tue, 5 Jan 2016 02:15:26 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0

On 01/04/2016 04:17 PM, James Youngman wrote:
> Thanks.
> a) Comments on the patch:
> 1. Essentially the current version of configure.ac was written by me:

yes, right; so the patch boils down to the attached, updated patch.

> b) Sure, go ahead and push patches to the 4.6 branch.    Generally
> yes, for low-risk patches.

thanks, done.

> c) I'd like input from the other committers and from the principal
> downstream consumers (e.g. Andreas, Kamil) before making a choice,
> since it's the committers who would need to maintain the parallel
> branches and the downstream maintainers who (allegedly) benefit.
> Let's have a data-based discussion about what works for everyone - in
> a separate thread, I'd suggest.

Okay, I'll come up with something in a separate thread then.

> c, part 2) Happy to change the naming scheme, I'm not especially
> attached to the current one.

Unfortunately, the gain of having "git describe"-like tarball names
seems only to be possible once a 2-digit tag is in place.

> d) We could populate the .x file for files which will be persistently
> problematic (such as regexprops.texi).   I think fixing the
> translations will require coordination with the Translation Project.
> Or hacking the bootstrap script or the update-copyright script.

Other GNU projects don't have *.po files version-controlled nowadays,
because autopoint will always fetch the latest from TP.org.  As a side
effect, "make update-copyright" wouldn't have to be tamed to spare
these files.

Have a nice day,

Attachment: 0001-maint-add-copyright-header-to-configure.ac.patch
Description: Text Data

reply via email to

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