From: PAUL GILLIAM <pgilliam@us.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: jkingdon@engr.sgi.com, gdb-patches@sources.redhat.com
Subject: Re: using rsync to create local repository
Date: Thu, 26 Jan 2006 23:28:00 -0000 [thread overview]
Message-ID: <1138318142.1423.70.camel@dufur.beaverton.ibm.com> (raw)
In-Reply-To: <20060126205524.GA17357@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On Thu, 2006-01-26 at 15:55 -0500, Daniel Jacobowitz wrote:
> On Thu, Jan 26, 2006 at 12:53:40PM -0800, PAUL GILLIAM wrote:
> > On Thu, 2006-01-26 at 14:07 -0500, Daniel Jacobowitz wrote:
> > > On Thu, Jan 26, 2006 at 10:56:28AM -0800, PAUL GILLIAM wrote:
> > > > I tried a similar thing and it seemed to work:
> > > >
> > > > rsync --archive --delete --compress --progress \
> > > > --exclude '#cvs.*' --exclude 'CVSROOT/config' \
> > > > --exclude 'CVSROOT/history' --exclude 'CVSROOT/updatelog' \
> > > > rsync://sources.redhat.com/gdb-cvs /home/pgilliam/gdb/gdb-cvs
> > >
> > > Wrong repository. You want src-cvs, not gdb-cvs, which only has the
> > > web pages in it.
> > >
> > Ahhh. That would explain it.
> >
> > Would it be useful for me to submit a patch that would add this
> > information to one of those web pages?
>
> I suppose.
>
Daniel, please try to restrain your enthusiasm 8-)
I have attached the patch, OK to commit?
-=# Paul #=-
PS: It looks like there is no ChangeLog for the web pages, so I did not
include an entry for one.
[-- Attachment #2: rsync.patch --]
[-- Type: text/x-patch, Size: 1171 bytes --]
Index: index.html
===================================================================
RCS file: /cvs/gdb/htdocs/current/index.html,v
retrieving revision 1.35
diff -a -u -r1.35 index.html
--- index.html 2 Nov 2005 21:58:50 -0000 1.35
+++ index.html 26 Jan 2006 23:20:22 -0000
@@ -148,6 +148,21 @@
<p>
+<li><b>CVS via rsync</b> (rarely used):<p>
+
+Under rare circumstances, it is desirable to maintain a local copy of
+the complete CVS repository. Anonymous <code>rsync</code> access has
+been is available for that purpose. Here is how to get a copy of the
+repository, or to synchronize an existing one:
+
+<pre>
+rsync --archive --delete --compress rsync://sources.redhat.com/src-cvs src-cvs </pre>
+
+You can get <code>rsync</code> or learn more about it from its home page:
+<a href:"http://rsync.samba.org"> rsync.samba.org</a>
+
+<p>
+
<li><b>FTP</b>:<p>
A daily snapshot of the current development sources (<a
@@ -260,7 +275,7 @@
<p>Verbatim copying and distribution of this entire article is
permitted in any medium, provided this notice is preserved.</p>
-<p>Last modified 2005-10-25.</p>
+<p>Last modified 2006-01-26.</p>
</address>
</body>
next parent reply other threads:[~2006-01-26 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1138301788.1423.54.camel@dufur.beaverton.ibm.com>
[not found] ` <20060126190733.GA13020@nevyn.them.org>
[not found] ` <1138308820.1423.59.camel@dufur.beaverton.ibm.com>
[not found] ` <20060126205524.GA17357@nevyn.them.org>
2006-01-26 23:28 ` PAUL GILLIAM [this message]
2006-02-01 23:43 ` Daniel Jacobowitz
2006-02-03 22:58 ` PAUL GILLIAM
2006-02-06 21:20 ` Daniel Jacobowitz
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=1138318142.1423.70.camel@dufur.beaverton.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jkingdon@engr.sgi.com \
/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