From: Karel Zak <kzak@redhat.com>
To: Petr Uzel <petr.uzel@suse.cz>
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 1/2] blkid: use symbolic exit code
Date: Wed, 23 May 2012 09:45:56 +0200 [thread overview]
Message-ID: <20120523074556.GG14560@x2.net.home> (raw)
In-Reply-To: <1337157512-31920-1-git-send-email-petr.uzel@suse.cz>
On Wed, May 16, 2012 at 10:38:31AM +0200, Petr Uzel wrote:
> misc-utils/blkid.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Applied, thanks.
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2012-05-23 7:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 8:38 [PATCH 1/2] blkid: use symbolic exit code Petr Uzel
2012-05-16 8:38 ` [PATCH 2/2] blkid: introduce symbolic names for different blkid exit codes Petr Uzel
2012-05-16 8:52 ` Voelker, Bernhard
2012-05-16 9:24 ` Petr Uzel
2012-05-16 10:13 ` Karel Zak
2012-05-16 11:18 ` Voelker, Bernhard
2012-05-17 7:37 ` [PATCH] blkid: stop device probing if error is detected Petr Uzel
2012-05-23 7:46 ` Karel Zak
2012-05-23 7:46 ` [PATCH 2/2] blkid: introduce symbolic names for different blkid exit codes Karel Zak
2012-05-23 7:45 ` Karel Zak [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=20120523074556.GG14560@x2.net.home \
--to=kzak@redhat.com \
--cc=petr.uzel@suse.cz \
--cc=util-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).