From: Scott Moser <smoser@ubuntu.com>
To: Phillip Susi <psusi@ubuntu.com>
Cc: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Subject: Re: [PATCH] fix partx --update ranges and out of order tables
Date: Tue, 14 Jan 2014 09:53:42 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1401140952480.5329@brickies> (raw)
In-Reply-To: <52D54D09.10506@ubuntu.com>
On Tue, 14 Jan 2014, Phillip Susi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > +blkid_partition get_partition_by_partno(blkid_partlist ls, int n)
>
> I was wondering why libblkid didn't already have a function like this,
> should this be moved there instead of just being in partx.c?
I figured I'd leave that up to upstream.
I had an implementation of that, but didn't know of the policy for adding
stuff to libblkid. This was less invasive. I'm fine with libblkid also.
Scott
next prev parent reply other threads:[~2014-01-14 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 20:32 [PATCH] fix partx --update ranges and out of order tables Scott Moser
2014-01-14 8:54 ` Karel Zak
2014-01-14 14:41 ` Scott Moser
2014-01-14 14:43 ` Phillip Susi
2014-01-14 14:53 ` Scott Moser [this message]
2014-01-14 15:21 ` Phillip Susi
2014-01-15 9:55 ` Karel Zak
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=alpine.DEB.2.02.1401140952480.5329@brickies \
--to=smoser@ubuntu.com \
--cc=kzak@redhat.com \
--cc=psusi@ubuntu.com \
--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