From: Anil Kumar Sharma <xplusaks@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Newbie of LVM
Date: Sat, 10 Dec 2005 01:33:59 +0530 [thread overview]
Message-ID: <52fe6b680512091203v451e17b1m81491000c0077b41@mail.gmail.com> (raw)
In-Reply-To: <52fe6b680512091157j2cec853ey557d0bb3133d298e@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 107 bytes --]
This list moves fast....4 hits before a send button hit.... brief is a
word..
--
Anil Kumar Shrama
[-- Attachment #2: Type: text/html, Size: 174 bytes --]
next prev parent reply other threads:[~2005-12-09 20:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 3:39 [linux-lvm] Newbie of LVM Way Loss
2005-12-09 18:50 ` Anil Kumar Sharma
2005-12-09 19:12 ` Matthew Gillen
2005-12-09 19:38 ` Jeff Cousino
2005-12-09 19:43 ` Matthew Gillen
2005-12-09 19:48 ` Graham Wood
2005-12-09 19:42 ` Matthew Gillen
2005-12-09 19:57 ` Anil Kumar Sharma
2005-12-09 20:03 ` Anil Kumar Sharma [this message]
2005-12-12 15:21 ` Alasdair G Kergon
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=52fe6b680512091203v451e17b1m81491000c0077b41@mail.gmail.com \
--to=xplusaks@gmail.com \
--cc=linux-lvm@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 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).