From: Conway Yee <yee@bronze.lcs.mit.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug fix to oct 14 release
Date: Thu, 19 Oct 2000 14:14:30 +0000 [thread overview]
Message-ID: <bqwvguprlfw.fsf@bronze.lcs.mit.edu> (raw)
In-Reply-To: <20001018165147.091C4199CF@mail>
How are releases put together? I don't suppose that you simply
run tar on an existing source tree. How does one miss scattered
files?
Conway Yee
next prev parent reply other threads:[~2000-10-19 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-18 16:51 Russ Cox
2000-10-19 14:14 ` Conway Yee [this message]
2000-10-19 15:47 rob pike
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=bqwvguprlfw.fsf@bronze.lcs.mit.edu \
--to=yee@bronze.lcs.mit.edu \
--cc=9fans@cse.psu.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).