From: Ian Abbott <abbotti@mev.co.uk>
To: barebox@lists.infradead.org, Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: Stable branches resurrected
Date: Wed, 24 May 2017 16:13:13 +0100 [thread overview]
Message-ID: <c7e87a03-b1a7-209c-12a0-f984b2553754@mev.co.uk> (raw)
In-Reply-To: <20170524073627.dqfb7v7td3utbcos@pengutronix.de>
On 24/05/17 08:36, Sascha Hauer wrote:
> Hi All,
>
> v2017.05.0 contains some nasty bugs. This led me to the idea to
> resurrect the stable branches. I created stable/v2017.05 and also
> released v2017.05.1. Please update to this one if you are using
> v2017.05.0.
>
> Experience shows that very few people semm to test the master branch,
> but that I get bug reports relatively fast after a release. I'll try and
> collect at least the bugfixes for the current release in a stable
> branch. I'm not yet sure how long I maintain each stable branch though,
> probably not too long to keep people motivated to update ;)
>
> If you want to have a patch in a stable branch, please tell me so to
> keep me reminded that we have these branches.
The only one I can think of at the moment for the 2017.05 series is
commit eaf884ba55def055fd81ff3291a1a534fc8bd8f9 ("nv: Fix setting of
nv.dev.<devname>.<param> variables").
Best regards,
Ian.
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-05-24 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 7:36 Sascha Hauer
2017-05-24 15:13 ` Ian Abbott [this message]
2017-05-30 6:10 ` Sascha Hauer
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=c7e87a03-b1a7-209c-12a0-f984b2553754@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox