From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: Karel Zak <kzak@redhat.com>, Bernhard Voelker <mail@bernhard-voelker.de>
Cc: util-linux@vger.kernel.org
Subject: Re: stable/v2.29.1
Date: Thu, 19 Jan 2017 10:09:30 -0600 [thread overview]
Message-ID: <5880E4BA.9090703@gmail.com> (raw)
In-Reply-To: <20170119113502.ykteazztzpd7eocs@ws.net.home>
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.
That is certainly true for Linux From Scratch.
-- Bruce
prev parent reply other threads:[~2017-01-19 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 13:12 stable/v2.29.1 Karel Zak
2017-01-19 10:32 ` stable/v2.29.1 Bernhard Voelker
2017-01-19 11:35 ` stable/v2.29.1 Karel Zak
2017-01-19 12:15 ` stable/v2.29.1 Bernhard Voelker
2017-01-19 12:46 ` stable/v2.29.1 Karel Zak
2017-01-19 16:09 ` Bruce Dubbs [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5880E4BA.9090703@gmail.com \
--to=bruce.dubbs@gmail.com \
--cc=kzak@redhat.com \
--cc=mail@bernhard-voelker.de \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.