From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lvm2: bump version to 2.02.113
Date: Fri, 28 Nov 2014 09:43:30 +0000 [thread overview]
Message-ID: <547843C2.4010207@imgtec.com> (raw)
In-Reply-To: <20141127225834.4495b58f@free-electrons.com>
Dear Peter and Thomas,
On 11/27/2014 09:58 PM, Thomas Petazzoni wrote:
> Peter,
>
> On Thu, 27 Nov 2014 22:52:34 +0100, Peter Korsgaard wrote:
>
>> > Applied, thanks.
>>
>> NIT: It's handy if you explicitly state that the patches are applied to the
>> next branch.
>
> Agreed, missed this detail in my notifications tonight, sorry about
> that.
>
> Thomas
>
sorry guys, I will add that information to my commit messages in future
patches for the next branch.
Cheers,
--
Vicente Olivert Riera
Graduate Software Engineer, MIPS Platforms
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com
next prev parent reply other threads:[~2014-11-28 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 14:00 [Buildroot] [PATCH] lvm2: bump version to 2.02.113 Vicente Olivert Riera
2014-11-27 19:32 ` Thomas Petazzoni
2014-11-27 21:52 ` Peter Korsgaard
2014-11-27 21:58 ` Thomas Petazzoni
2014-11-28 9:43 ` Vicente Olivert Riera [this message]
2014-11-28 9:47 ` Peter Korsgaard
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=547843C2.4010207@imgtec.com \
--to=vincent.riera@imgtec.com \
--cc=buildroot@busybox.net \
/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