From: Karel Zak <kzak@redhat.com>
To: Davidlohr Bueso <dave@gnu.org>
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 1/5] fdisk: api: propagate partition deletion to users
Date: Thu, 18 Oct 2012 12:19:09 +0200 [thread overview]
Message-ID: <20121018101909.GC16021@x2.net.home> (raw)
In-Reply-To: <1349620417.2548.6.camel@offbook>
On Sun, Oct 07, 2012 at 04:33:37PM +0200, Davidlohr Bueso wrote:
> fdisks/fdisk.h | 2 +-
> fdisks/fdiskbsdlabel.c | 6 ++++--
> fdisks/fdiskdoslabel.c | 4 +++-
> fdisks/fdisksgilabel.c | 13 ++++++++-----
> fdisks/fdisksunlabel.c | 12 +++++++-----
> fdisks/gpt.c | 8 +++++---
> fdisks/utils.c | 3 +--
> 8 files changed, 33 insertions(+), 21 deletions(-)
Applied, thanks.
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2012-10-18 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 14:33 [PATCH 1/5] fdisk: api: propagate partition deletion to users Davidlohr Bueso
2012-10-10 8:17 ` Petr Uzel
2012-10-18 10:19 ` 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=20121018101909.GC16021@x2.net.home \
--to=kzak@redhat.com \
--cc=dave@gnu.org \
--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).