From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: Source version control (Was: [9fans] lucio-)
Date: Thu, 10 Jan 2002 13:18:12 +0100 [thread overview]
Message-ID: <20020110121827.91C85199B9@mail.cse.psu.edu> (raw)
Why don't you just change the implementation of the file server
to accept a remote 'dump name' command to cause an immediate dump at root
/n/dump/name/ ?
Of course this would need to implement something like a /ctl file
on the file server to accept innocent-looking(?) commands from other machines.
next reply other threads:[~2002-01-10 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 12:18 Fco.J.Ballesteros [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-09 5:08 [9fans] lucio- Russ Cox
2002-01-09 5:32 ` Lucio De Re
2002-01-10 10:37 ` Bruce Janson
2002-01-10 12:07 ` Source version control (Was: [9fans] lucio-) Lucio De Re
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=20020110121827.91C85199B9@mail.cse.psu.edu \
--to=nemo@plan9.escet.urjc.es \
--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).