From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Some MFT doc fixes.
Date: Tue, 05 Feb 2002 11:50:55 -0500 [thread overview]
Message-ID: <2npu3jyis0.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <877kpse62s.fsf@cs.utah.edu> (Sriram Karra's message of "Tue, 05 Feb 2002 13:03:15 +0530")
Sriram Karra <karra@cs.utah.edu> writes:
> This patch improves the MFT documentation as per the suggestions of
> Matt Armstrong (Message-ID: <87wuyyaw21.fsf@squeaker.lickey.com>) and
> Benjamin Rutt (<wc3sn9m0xi6.fsf@eta.cis.ohio-state.edu>)
Installed.
ShengHuo
prev parent reply other threads:[~2002-02-05 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 7:33 Sriram Karra
2002-02-05 16:50 ` ShengHuo ZHU [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=2npu3jyis0.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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).