From: Fco.J.Ballesteros <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: [9fans] sources dump?
Date: Thu, 4 Mar 2004 08:42:52 +0100 [thread overview]
Message-ID: <85045dda04ff8bb77dd5d794b57891b8@plan9.escet.urjc.es> (raw)
I know that can be done locally at each of our sites, but,
wouldn't it be good to have the sources fs archived so that
anyone could mount sources/archive and see what a previous
official distribution was?
I've been missing that, although I just keep a local copy of
that part that we have changed locally. But I think that could
be a nice tool for those that are used to make local changes.
Just a thought.
next reply other threads:[~2004-03-04 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 7:42 Fco.J.Ballesteros [this message]
[not found] <18335250743f714bba76213eba1a47ec@proxima.alt.za>
2004-03-04 7:51 ` Fco.J.Ballesteros
2004-03-04 7:58 ` Kenji Okamoto
2004-03-04 8:00 ` Fco.J.Ballesteros
2004-03-04 8:04 ` Kenji Okamoto
2004-03-04 8:27 ` Kenji Okamoto
2004-03-04 8:40 ` Kenji Okamoto
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=85045dda04ff8bb77dd5d794b57891b8@plan9.escet.urjc.es \
--to=nemo@lsub.org \
--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).