From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: Is the gnus XEmacs package still necessary?
Date: Wed, 19 Jul 2000 12:59:43 -0400 [thread overview]
Message-ID: <00Jul19.125945edt.115206@gateway.intersys.com> (raw)
In-Reply-To: Steinar Bang's message of "19 Jul 2000 11:38:10 +0200"
* Steinar Bang <sb@metis.no> on Wed, 19 Jul 2000
| What's the gain from unpacking the tarball first? Does it have files
| that are no longer in the CVS?
Last time I tried the CVS, shortly before 5.8.7 went out the door, this was
the case.
--
Rat <ratinox@peorth.gweep.net> \ Happy Fun Ball contains a liquid core,
Minion of Nathan - Nathan says Hi! \ which, if exposed due to rupture, should
PGP Key: at a key server near you! \ not be touched, inhaled, or looked at.
prev parent reply other threads:[~2000-07-19 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-18 1:43 Lloyd Zusman
2000-07-18 2:04 ` Daniel Pittman
2000-07-18 2:10 ` Lloyd Zusman
2000-07-18 2:20 ` Daniel Pittman
2000-07-18 2:34 ` Lloyd Zusman
2000-07-18 2:24 ` Vin Shelton
2000-07-18 2:27 ` Lloyd Zusman
2000-07-18 2:31 ` Lloyd Zusman
2000-07-18 4:02 ` Cyrille Lefevre
2000-07-18 2:26 ` Stainless Steel Rat
2000-07-19 9:38 ` Steinar Bang
2000-07-19 16:59 ` Stainless Steel Rat [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=00Jul19.125945edt.115206@gateway.intersys.com \
--to=ratinox@peorth.gweep.net \
/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).