From: Ian Abbott <abbotti@mev.co.uk>
To: barebox@lists.infradead.org
Subject: Re: v2017.06.0
Date: Tue, 13 Jun 2017 12:53:17 +0100 [thread overview]
Message-ID: <56502b6d-3551-03c6-fb74-b37e51b92530@mev.co.uk> (raw)
In-Reply-To: <20170613113820.f2jr6tqpt63bdymu@pengutronix.de>
On 13/06/17 12:38, Sascha Hauer wrote:
> On Tue, Jun 13, 2017 at 10:52:33AM +0100, Ian Abbott wrote:
>> On 13/06/17 10:43, Ian Abbott wrote:
>>> On 13/06/17 10:42, Ian Abbott wrote:
>>>> On 13/06/17 08:53, Sascha Hauer wrote:
>>>>> barebox v2017.06.0 is available. I originally wanted to wait for the
>>>>> fix of the OMAP Nand controller issue, but unfortunately there's no
>>>>> full solution in sight. Since waiting longer would effectively mean that
>>>>> we skip the June release, I decided to do a release with this bug still
>>>>> standing.
>>>>
>>>> Thanks Sasha. Could you git push the release, please?
>>>
>>> I mean "Sascha". Sorry!
>>
>> Oh, I see the tag is in the repository, but it's currently three commits
>> ahead of origin/master.
>
> Try again, forgot to push master.
Thanks. All okay now.
--
-=( 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
prev parent reply other threads:[~2017-06-13 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 7:53 v2017.06.0 Sascha Hauer
2017-06-13 9:42 ` v2017.06.0 Ian Abbott
2017-06-13 9:43 ` v2017.06.0 Ian Abbott
2017-06-13 9:52 ` v2017.06.0 Ian Abbott
2017-06-13 11:38 ` v2017.06.0 Sascha Hauer
2017-06-13 11:53 ` Ian Abbott [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=56502b6d-3551-03c6-fb74-b37e51b92530@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox