Re: stable/v2.29.1

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

 



On 01/19/2017 12:35 PM, Karel Zak wrote:
> On Thu, Jan 19, 2017 at 11:32:20AM +0100, Bernhard Voelker wrote:
>> On 01/18/2017 02:12 PM, Karel Zak wrote:
>>> The branch stable/v2.29 contains what I want to release as v2.29.1.
>>
>> General question:
>> Is it worth dealing with maintenance branches in the upstream repo?
>> I mean, downstream projects can cherry-pick fixes and improvements
>> to their own needs anyway.  So I think having one upstream mainline
>> would be sufficient.  WDYT?
> 
>  I use the branches to create maintenance releases (tarballs), e.g.
>  v2.29.1.
>  
>  The goal is to minimize number of patches in downstream packages. So I
>  guess downstream are happy to have .1 and .2 releases.

I see: as you're also downstream Redhat/Fedora maintainer, you're
effectively doing the downstream work in the upstream repository and
thus share this to other projects.  That's nice. ;-)

Thanks & have a nice day,
Berny

--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux