All of lore.kernel.org
 help / color / mirror / Atom feed
From: Curtis Gedak <gedakc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Hannes Reinecke <hare-l3A5Bk7waGM@public.gmane.org>
Cc: parted-devel-XbBxUvOt3X2LieD7tvxI8l/i77bcL1HB@public.gmane.org,
	device-mapper development
	<dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org,
	Phillip Susi <psusi-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>,
	Debian LVM Team
	<pkg-lvm-maintainers-XbBxUvOt3X2LieD7tvxI8l/i77bcL1HB@public.gmane.org>
Subject: Re: [dm-devel] What is the deal with the partition separator?
Date: Thu, 17 Feb 2011 09:54:32 -0700	[thread overview]
Message-ID: <4D5D52C8.3080706@gmail.com> (raw)
In-Reply-To: <4D5D3B34.4000005-l3A5Bk7waGM@public.gmane.org>

On 11-02-17 08:13 AM, Hannes Reinecke wrote:
> So whichever way you proceed, you should avoid using a naming scheme
> which resembles the linux one.

 From my perspective as a maintainer of partitioning software it would 
be nice if given the device name and partition number I could easily 
determine the partition name.

Unfortunately this is not easily done when there are deviations from the 
linux model ("insert a 'p' between the device name and the partition 
number when the device name ends in a number").

Each deviation from the linux partition naming model results in more 
code to handle the deviation, and a corresponding increased number of 
test cases to avoid errors.

Regards,
Curtis Gedak
(Maintainer of GParted)

      parent reply	other threads:[~2011-02-17 16:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16  3:21 What is the deal with the partition separator? Phillip Susi
2011-02-16  7:38 ` Hannes Reinecke
     [not found]   ` <4D5B7ED9.20304-l3A5Bk7waGM@public.gmane.org>
2011-02-16 17:19     ` [dm-devel] " Curtis Gedak
     [not found]       ` <4D5C073F.3020502-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-02-16 19:33         ` Phillip Susi
     [not found]           ` <4D5C268B.6070507-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-02-16 20:18             ` Curtis Gedak
2011-02-16 19:37     ` Phillip Susi
     [not found]       ` <4D5C2793.1020601-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-02-17  7:29         ` Hannes Reinecke
     [not found]           ` <4D5CCE75.5090202-l3A5Bk7waGM@public.gmane.org>
2011-02-17 14:57             ` Phillip Susi
     [not found]               ` <4D5D375F.9070106-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-02-17 15:13                 ` Hannes Reinecke
     [not found]                   ` <4D5D3B34.4000005-l3A5Bk7waGM@public.gmane.org>
2011-02-17 15:13                     ` Phillip Susi
2011-02-17 16:53                       ` Alasdair G Kergon
2011-02-17 16:58                         ` Alasdair G Kergon
     [not found]                         ` <20110217165332.GE28729-FDJ95KluN3Z0klwcnFlA1dvLeJWuRmrY@public.gmane.org>
2011-02-20  5:04                           ` [dm-devel] " Phillip Susi
2011-02-17 16:54                     ` Curtis Gedak [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=4D5D52C8.3080706@gmail.com \
    --to=gedakc-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=hare-l3A5Bk7waGM@public.gmane.org \
    --cc=parted-devel-XbBxUvOt3X2LieD7tvxI8l/i77bcL1HB@public.gmane.org \
    --cc=pkg-lvm-maintainers-XbBxUvOt3X2LieD7tvxI8l/i77bcL1HB@public.gmane.org \
    --cc=psusi-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org \
    --cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.