From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] mtd-utils update / fixes
Date: Wed, 14 Mar 2012 11:08:33 +0100 [thread overview]
Message-ID: <20120314100833.GC20481@pengutronix.de> (raw)
In-Reply-To: <1331667959-53687-1-git-send-email-bernhard@bwalle.de>
On Tue, Mar 13, 2012 at 08:45:57PM +0100, Bernhard Walle wrote:
> This is the 2nd/3rd version of the patches. Hopefully the last round.
>
> Sorry for the confusion today. Too many machines, branches and too much work at
> the same time. :(
No problem. The series file still referred to the 3rd patch. I've fixed
that and applied both patches.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-03-14 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 19:45 Bernhard Walle
2012-03-13 19:45 ` [ptxdist] [PATCH 1/2] Update mtd-utils to 1.4.9 Bernhard Walle
2012-03-13 19:45 ` [ptxdist] [PATCH 2/2] mtd-utils.in: Add busybox dependencies Bernhard Walle
2012-03-14 10:08 ` Michael Olbrich [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=20120314100833.GC20481@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@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