From: categories <cat-dist@mta.ca>
To: categories <categories@mta.ca>
Subject: Re: e-prints
Date: Fri, 5 Dec 1997 08:46:01 -0400 (AST) [thread overview]
Message-ID: <Pine.OSF.3.90.971205084546.8443K-100000@mailserv.mta.ca> (raw)
Date: Thu, 4 Dec 1997 13:51:23 -0800 (PST)
From: john baez <baez@math.ucr.edu>
Michael Barr writes:
> I am all in favor of Jim Stasheff's proposal, but what does one do about
> the fact that I, for example, have my own personal macros files and
> my TeX files cannot be compiled without them.
Preprint servers of the sort Jim is describing have facilities for
uploading macro files, postscript files, etc. along with the TeX
files. I use them a lot and they work.
Best,
John Baez
next reply other threads:[~1997-12-05 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-05 12:46 categories [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-12-06 20:12 e-prints categories
1997-12-05 12:45 e-prints categories
1997-12-04 20:43 e-prints categories
1997-12-04 13:48 e-prints categories
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=Pine.OSF.3.90.971205084546.8443K-100000@mailserv.mta.ca \
--to=cat-dist@mta.ca \
--cc=categories@mta.ca \
/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).