Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Andrew Shugg <andrew@neep.com.au>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Oops on 2.4.20-pa33
Date: Fri, 9 May 2003 10:37:47 +0800	[thread overview]
Message-ID: <20030509103745.H20047@neep.com.au> (raw)
In-Reply-To: <20030507175155.GJ27494@lug-owl.de>; from jbglaw@lug-owl.de on Wed, May 07, 2003 at 07:51:55PM +0200

Jan-Benedict Glaw said:
> Thanks. This reminds me that I'd still *love* to see the CVS repository
> rsync'able. That'd really help me. However, it's at least nice to be
> basically able to rsync the checked-out source trees.
> 
> Any chances for a rsync for the CVS repo?
> 
> MfG, JBG

I'm not sure why you'd want to be able to rsync the entire repository,
unless you want to be able to track multiple branches of a module
without having to have a full checkout of each one?  That would make
more sense I guess, if you live in a world where the Internet is slow
and bandwidth is not free (I live there too, small world!).

There is already an rsync server running on ftp.parisc-linux.org, but I
don't believe it's widely advertised.

I just ran an 'rsync -va ftp.parisc-linux.org.au::pub' (the only rsync
'module' available) and the output was 14M!  Presumably this caused a
fair bit of thrashing at f.p-l.o's end as well ...

If you'd like to see what's available by rsync, I've compressed that
listing and uploaded it here.

ftp://ftp.neep.com.au/pub/parisc-linux/ftp.parisc-linux.org-rsync.txt.bz2

I'll have a trundle through it myself today, to see if I can write a
helpful motd for rsyncd and suggest how the ::pub module can be split up
into more useful bits.  (Bame, may I assume that you're still nominally
in charge of the rsyncd server?)

Andrew.

-- 
Andrew Shugg <andrew@neep.com.au>                   http://www.neep.com.au/

"Just remember, Mr Fawlty, there's always someone worse off than yourself."
"Is there?  Well I'd like to meet him.  I could do with a good laugh."

  reply	other threads:[~2003-05-09  2:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-05 20:02 [parisc-linux] Oops on 2.4.20-pa33 Jan-Benedict Glaw
2003-05-05 20:05 ` Randolph Chung
2003-05-05 21:05   ` [parisc-linux] [PATCH-2.4] DIVA serial build error (was: Oops on 2.4.20-pa33) Jan-Benedict Glaw
2003-05-06 15:20     ` Jan-Benedict Glaw
2003-05-07 16:27       ` Paul Bame
2003-05-06  6:04   ` [parisc-linux] Oops on 2.4.20-pa33 Joel Soete
2003-05-06 14:04     ` Randolph Chung
2003-05-06 15:04       ` Joel Soete
2003-05-06 15:08         ` Randolph Chung
2003-05-06 16:34         ` Joel Soete
2003-05-06 16:42           ` John David Anglin
2003-05-06 17:56             ` Joel Soete
2003-05-07 15:48               ` Jan-Benedict Glaw
2003-05-07 16:09                 ` Joel Soete
2003-05-07 17:17                   ` Randolph Chung
2003-05-07 17:51                     ` Jan-Benedict Glaw
2003-05-09  2:37                       ` Andrew Shugg [this message]
2003-05-09 22:04                         ` Jan-Benedict Glaw
2003-05-08  5:52                     ` Joel Soete
2003-05-08  6:12               ` [parisc-linux] [PATCH-linux-2.5] sa_handler compare with cast Jan-Benedict Glaw
2003-05-10 20:31             ` [parisc-linux] Yet another '__canonicalize_funcptr_for_compare' pb Joel Soete
2003-05-10 20:25               ` Jan-Benedict Glaw
2003-05-10 21:08               ` Grant Grundler
2003-05-10 21:32                 ` John David Anglin
2003-05-10 21:33                 ` Joel Soete
2003-05-10 21:38                   ` [parisc-linux] Yet another '__canonicalize_funcptr_for_compare' John David Anglin
2003-05-10 21:21               ` [parisc-linux] Re: Yet another '__canonicalize_funcptr_for_compare' pb John David Anglin
2003-05-05 20:10 ` [parisc-linux] Oops on 2.4.20-pa33 John David Anglin
  -- strict thread matches above, loose matches on Subject: below --
2003-05-06 17:33 Joel Soete
2003-05-06 17:40 ` Randolph Chung

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=20030509103745.H20047@neep.com.au \
    --to=andrew@neep.com.au \
    --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