All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Wysochanski <dwysocha@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH] Add escape sequence for ':' in command's PV list
Date: Fri, 15 May 2009 08:27:40 -0400	[thread overview]
Message-ID: <1242390460.2506.8.camel@f10-node1> (raw)
In-Reply-To: <1242389250.2506.6.camel@f10-node1>

On Fri, 2009-05-15 at 08:07 -0400, Dave Wysochanski wrote:
> On Thu, 2009-05-14 at 15:25 -0400, Dave Wysochanski wrote:
> > On Thu, 2009-05-14 at 11:33 +0200, Peter Rajnoha wrote: 
> > > On 05/13/2009 09:43 PM, Dave Wysochanski wrote:
> > > > I know, it does not make sense to specify a pe range
> > > > for pvcreate or vgcreate.  But shouldn't we be consistent, or at least
> > > > very much clarify the arguments are different?  I can just imagine
> > > > someone scripting something and then being surprised when they needed to
> > > > quote only for lvcreate, pvmove, etc.
> > > 
> > > Hmm, then the question is, what should we do with single unescaped ':' if
> > > it appears in pvcreate, vgcreate, e.g. "pvcreate /dev/a::b:c" -- the first
> > > double one is OK, but what about the second single one? Should it be considered
> > > as an input error then? (...probably giving the user a message like
> > > "PE range definition not allowed here.")
> > > 
> > 
> > At this point I'd lean towards just clarifing the difference in the
> > arguments for the commands (e.g. in man pages, etc).  See attached patch
> > for a stab at updating the man pages.  If we go this route, then your
> > patch is fine as is IMO.
> > 
> > Also, on IRC yesterday, Alasdair suggested a new built-in command to
> > escape names such as this 
> > 17:01:40 < deepthot> agk_: on the escaping, you mean someone would do something like: lvcreate -L 16M -n lvname vgname `lvmescape /dev/pname`?
> > 17:05:07 < agk_> almost:   lvmescape /dev/path   then they can append :4-10 on it
> > 
> > IMO, this is a good idea.  However, in the spirit of not getting too
> > sidetracked, I think if we add proper explanation, we can probably defer
> > adding the built-in command, which probably requires some design thought
> > (for example, how to specify whether it is a pvname, vgname, etc - they
> > may have different characters to escape, etc).  If you want to tackle
> > that too though, go for it.
> > 
> 
> Upon further thought, I agree with you Peter - let's reject the ":" in
> pvcreate/vgcreate commands and print a message about pe range not
> allowed in these commands.  This way the commands are all consistent -
> require a "::" if any pvname contains a ":" in any of the commands.
> 

Updated man page patch is attached.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Update-man-pages-to-clarify-usage-of-PE-ranges-and.patch
Type: text/x-patch
Size: 5575 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/lvm-devel/attachments/20090515/284e1366/attachment.bin>

  reply	other threads:[~2009-05-15 12:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 11:09 [PATCH] Add escape sequence for ':' in command's PV list Peter Rajnoha
2009-05-13 19:43 ` Dave Wysochanski
2009-05-13 19:55   ` Milan Broz
2009-05-14  9:33   ` Peter Rajnoha
2009-05-14 19:25     ` Dave Wysochanski
2009-05-15 12:07       ` Dave Wysochanski
2009-05-15 12:27         ` Dave Wysochanski [this message]
2009-05-15 17:57           ` Peter Rajnoha
2009-05-15 18:13             ` Alasdair G Kergon
  -- strict thread matches above, loose matches on Subject: below --
2010-09-15 12:30 Peter Rajnoha

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=1242390460.2506.8.camel@f10-node1 \
    --to=dwysocha@redhat.com \
    --cc=lvm-devel@redhat.com \
    /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.