From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: rsync for CVS repository
Date: Mon, 19 Nov 2001 10:50:54 +0100 [thread overview]
Message-ID: <20011119105054.B28328@lug-owl.de> (raw)
In-Reply-To: <1006094625.3bf7c921363b6@webmail.tiscalinet.be>
On Sun, 2001-11-18 15:43:45 +0100, joel.soete@freebel.net <joel.soete@freebel.net>
wrote in message <1006094625.3bf7c921363b6@webmail.tiscalinet.be>:
> Hi Paul,
>
> One great stuff which makes me prefer rsync versus cvs is that rsync allow me to
> define easily RSYNC_PROXY (afaik cvs did not) and in my working environement
> (behing a fw configure by neanderthal admin) it is a great help.
>
> But I also understand well your position.
Well, you don't need to advertise or document rsync access. People
interested in using it know how to do it, and they'll simply try
it. Look at oss.sgi.com - you won't really find rsync mentioned
there:-)
MfG, JBG
--
Jan-Benedict Glaw . jbglaw@lug-owl.de . +49-172-7608481
http://lug-owl.de/~jbglaw/software/snapshot2cvs/
next prev parent reply other threads:[~2001-11-19 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BF7C6E2.D6B35170@freebel.net>
2001-11-18 14:43 ` [parisc-linux] Re: rsync for CVS repository joel.soete
2001-11-19 9:50 ` Jan-Benedict Glaw [this message]
2001-11-19 18:46 ` Richard Higson
2001-11-15 13:49 Neulinger, Nathan
-- strict thread matches above, loose matches on Subject: below --
2001-11-14 23:51 rsync for CVS repository (was: Re: [parisc-linux] 2.4.14-pa1 seems to works fine on my B180) Jan-Benedict Glaw
2001-11-15 1:05 ` [parisc-linux] Re: rsync for CVS repository Grant Grundler
2001-11-15 1:39 ` Rafael Herrera
2001-11-15 2:47 ` Paul Bame
2001-11-15 4:20 ` Rafael Herrera
2001-11-15 12:28 ` Jan-Benedict Glaw
2001-11-19 13:56 ` Andrew Shugg
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=20011119105054.B28328@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=parisc-linux@lists.parisc-linux.org \
/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