linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] document vol_id -L
Date: Mon, 22 Jan 2007 18:38:58 +0000	[thread overview]
Message-ID: <200701222139.05558.arvidjaar@mail.ru> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 471 bytes --]

On Monday 22 January 2007 00:54, Kay Sievers wrote:
> On 1/21/07, Andrey Borzenkov <arvidjaar@mail.ru> wrote:
> > vol_id is apparently the only portable (and sometimes simply the only)
> > way to get partition label (and UUID). This patch adds option to print
> > raw label as opposed to safe one.
>
> Applied.
>

OK here is documentation for it (I still do not understand why file generated 
at build time are kept in SCM, but well ...)

regards

-andrey

[-- Attachment #1.1.2: vol_id-L_man.patch --]
[-- Type: text/x-diff, Size: 1350 bytes --]

Subject: [PATCH] Document vol_id -L option

From: Andrey Borzenkov <arvidjaar@mail.ru>

Add description of -L to vol_id man page; point out difference between
safe label (-l) and raw version (-L)

Signed-off-by: Andrey Borzenkov <arvidjaar@mail.ru>

---

 extras/volume_id/vol_id.xml |   13 ++++++++++++-
 1 files changed, 12 insertions(+), 1 deletions(-)

diff --git a/extras/volume_id/vol_id.xml b/extras/volume_id/vol_id.xml
index b9b35ab..2b26b3b 100644
--- a/extras/volume_id/vol_id.xml
+++ b/extras/volume_id/vol_id.xml
@@ -59,7 +59,10 @@
           <varlistentry>
             <term><option>-l</option></term>
             <listitem>
-              <para>print the label of a volume</para>
+	      <para>
+		print the safe version of volume label suitable for
+		use as filename. Use <option>-L</option> to print literal label
+	      </para>
             </listitem>
           </varlistentry>
           <varlistentry>
@@ -68,6 +71,14 @@
               <para>print the uuid of a volume</para>
             </listitem>
           </varlistentry>
+          <varlistentry>
+            <term><option>-L</option></term>
+            <listitem>
+	      <para>
+		print raw volume label
+	      </para>
+            </listitem>
+          </varlistentry>
         </variablelist>
       </refsect1>
 

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 347 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 226 bytes --]

_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

                 reply	other threads:[~2007-01-22 18:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200701222139.05558.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --cc=linux-hotplug@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).