From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] e2fsprogs: bump to version 1.42.11
Date: Fri, 11 Jul 2014 15:19:51 -0300 [thread overview]
Message-ID: <53C02AC7.9050500@zacarias.com.ar> (raw)
In-Reply-To: <20140711200547.7bcb014d@free-electrons.com>
On 07/11/2014 03:05 PM, Thomas Petazzoni wrote:
> Applied, thanks. Next time, could you include in the commit log a
> description of why certain patches are kept and others are removed?
Sure, "they're upstream" ;)
The remaining patch is quite old from
44b5637ab28306dcd6f7a46aae56bdcf6284b3e7 (2009).
It might be worth checking if that's still required.
Regards.
prev parent reply other threads:[~2014-07-11 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 16:36 [Buildroot] [PATCHv2] e2fsprogs: bump to version 1.42.11 Gustavo Zacarias
2014-07-11 18:05 ` Thomas Petazzoni
2014-07-11 18:19 ` Gustavo Zacarias [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=53C02AC7.9050500@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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