From: Chris Mason <mason@suse.com>
To: "Martin.Knoblauch" <Martin.Knoblauch@TeraPort.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: ReiserFs: Cosmetic problem in linux/Documentation/Changes [2.4.x]
Date: Fri, 18 May 2001 16:58:44 -0400 [thread overview]
Message-ID: <179450000.990219524@tiny> (raw)
In-Reply-To: <3B0506C9.25966BCC@TeraPort.de>
On Friday, May 18, 2001 01:26:01 PM +0200 "Martin.Knoblauch"
<Martin.Knoblauch@TeraPort.de> wrote:
> "Martin.Knoblauch" wrote:
>>
>> Hi,
>>
>> I submitted this a short while ago, only to realize later that the
>> subject line was not very informative. Sorry.
>>
>> As a suggestion: maybe the reiser-tools should support the common
>> -V/--version flag
>>
Newer verions (at least 3.x.0j) have a -V.
-chris
prev parent reply other threads:[~2001-05-18 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-18 9:22 Cosmetic problem in Documentation/Changes [2.4.x] Martin.Knoblauch
2001-05-18 9:38 ` ReiserFs: Cosmetic problem in linux/Documentation/Changes [2.4.x] Martin.Knoblauch
2001-05-18 11:26 ` Martin.Knoblauch
2001-05-18 20:58 ` Chris Mason [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=179450000.990219524@tiny \
--to=mason@suse.com \
--cc=Martin.Knoblauch@TeraPort.de \
--cc=linux-kernel@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