From: Davidlohr Bueso <dave@gnu.org>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org, Petr Uzel <petr.uzel@suse.cz>
Subject: Re: libfdisk branch
Date: Fri, 07 Dec 2012 19:24:36 -0800 [thread overview]
Message-ID: <1354937076.2664.12.camel@offbook> (raw)
In-Reply-To: <20121206143527.GB4991@x2.net.home>
On Thu, 2012-12-06 at 15:35 +0100, Karel Zak wrote:
> Hi,
>
> I have created libfdisk branch at github. The most important change
> is libfdisk/ directory. The directory contains the new code from
> fdisks/utils.c (this file does not exist anymore). The goal is to
> create a code independent on the global variables mess in fdisks/.
Thanks for doing this Karel. I think this makes a lot of sense since
utils.c was starting to get messy (lots of different _layers_ together).
We also have to move the label files in libfdisk/, fdisks should only
have {c,s}fdisk.c
So fdisk patches should now be on top of this new branch, right?
>
> The library won't be distributed as shared library, it's libfdisk.la
> for the fdisk only (at least for now before the API will be stable
> and usable).
Agreed. This reminds me that we still haven't updated the fdisk manpage
for the gpt support. IIRC you like to release around now, if so, this is
something we need to get in.
Cheers,
Davidlohr
parent reply other threads:[~2012-12-08 3:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20121206143527.GB4991@x2.net.home>]
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=1354937076.2664.12.camel@offbook \
--to=dave@gnu.org \
--cc=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