Re: stable branches (was Re: [PATCH 0/8] maintenance patches)

2016-01-06 Thread Kamil Dudka
On Tuesday, January 05, 2016 17:28:03 James Youngman wrote: > On Tue, Jan 5, 2016 at 1:31 PM, Kamil Dudka wrote: > > On Monday 04 January 2016 15:17:24 James Youngman wrote: > >> c) I'd like input from the other committers and from the principal > >> downstream consumers (e.g. Andreas, Kamil) befo

Development and release model? - Multiple branches? (was: [PATCH 0/8] maintenance patches)

2016-01-05 Thread Andreas Metzler
On 2016-01-04 James Youngman wrote: > On Mon, Jan 4, 2016 at 8:11 AM, Bernhard Voelker > wrote: [...] >> b) Do you want me to push to the 4.6 branch, too? (see c)). >> c) Will we maintain a 4.6 and a 4.7 line in parallel (although >> we don't have anything big for master)? I must confess that >

Re: stable branches (was Re: [PATCH 0/8] maintenance patches)

2016-01-05 Thread James Youngman
On Tue, Jan 5, 2016 at 1:31 PM, Kamil Dudka wrote: > On Monday 04 January 2016 15:17:24 James Youngman wrote: >> 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 m

Re: stable branches (was Re: [PATCH 0/8] maintenance patches)

2016-01-05 Thread Bernhard Voelker
On 01/05/2016 02:31 PM, Kamil Dudka wrote: Fedora and RHEL maintainers backport mainly fixes for bugs that are reported via Red Hat Bugzilla. At the same time, we update to the latest upstream release in the development version of Fedora, from which the stable Fedora releases are branched each 6

stable branches (was Re: [PATCH 0/8] maintenance patches)

2016-01-05 Thread Kamil Dudka
On Monday 04 January 2016 15:17:24 James Youngman wrote: > 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 mainta

Re: [PATCH 0/8] maintenance patches

2016-01-04 Thread Bernhard Voelker
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.Generall

Re: [PATCH 0/8] maintenance patches

2016-01-04 Thread James Youngman
Thanks. a) Comments on the patch: 1. Essentially the current version of configure.ac was written by me: $ git shortlog -- configure.ac configure.in | grep '^[^ ]' Benedikt Morbach (1): Bernhard Voelker (2): Eric Blake (4): James Youngman (197): Jim Meyering (1): Kevin Dalley (12): Stefano Lattari

Re: [PATCH 0/8] maintenance patches

2016-01-04 Thread Bernhard Voelker
On 01/04/2016 01:37 AM, James Youngman wrote: > Thanks for doing this. > > Sorry about the mid-air collision on the copyright updates.All the > other patches look good to me, please apply! Thanks for the review - I pushed at the master branch. 4 questions: a) There are some parts left from

Re: [PATCH 0/8] maintenance patches

2016-01-03 Thread James Youngman
Thanks for doing this. Sorry about the mid-air collision on the copyright updates.All the other patches look good to me, please apply! On Mon, Jan 4, 2016 at 12:28 AM, Bernhard Voelker wrote: > The following is a list of minor maintenance patches: > > [PATCH 1/8] build: avoid bootstrap err

[PATCH 0/8] maintenance patches

2016-01-03 Thread Bernhard Voelker
The following is a list of minor maintenance patches: [PATCH 1/8] build: avoid bootstrap error on clean tree [PATCH 2/8] maint: remove po/Makevars as it is created during bootstrap [PATCH 3/8] maint: update .gitignore files, remove obsolete .cvsignore files [PATCH 4/8] maint: update all co