From: PAUL GILLIAM <pgilliam@us.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: using rsync to create local repository
Date: Fri, 03 Feb 2006 22:58:00 -0000 [thread overview]
Message-ID: <1139007553.1423.133.camel@dufur.beaverton.ibm.com> (raw)
In-Reply-To: <20060201234306.GD14187@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 2276 bytes --]
On Wed, 2006-02-01 at 18:43 -0500, Daniel Jacobowitz wrote:
> On Thu, Jan 26, 2006 at 03:29:02PM -0800, PAUL GILLIAM wrote:
> > +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:
>
> "has been is"; probably just want "is".
I guess I couldn't make up my mind 8-)
>
> > +
> > +<pre>
> > +rsync --archive --delete --compress rsync://sources.redhat.com/src-cvs src-cvs </pre>
>
> That's not the command you were using, is it? There were some
> --exclude options; without them you can't check out of the resulting
> tree and you waste a lot of bandwidth.
>
Damn! You're right. I don't know what I was thinking. Here is the
actual command I used:
rsync -az --delete --exclude '#cvs.*' --exclude 'CVSROOT/config' \
--exclude \ 'CVSROOT/history' --exclude 'CVSROOT/updatelog' \
rsync://sources.redhat.com/gdb-cvs gdb-cvs
I cribbed these from Janis Johnson as used for GCC. Do we need these
same excludes?
> > +
> > +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>
> Extra space before rsync.samba.org. There's supposed to be an = after
> href.
>
OK, attached is the new patch: OK to commit?
I have also attached a patch to MAINTAINERS in light of the following
e-mail exchange:
> Me: Are you the Jim Kingdon that was involved in GDB a few years ago?
> If so, should this file be updated to include your new e-mail address?
> It looks like the one in the MAINTAINERS file is 5 years out of date.
>
> Jim Kingdon: Yes, it is out of date. I was in touch with someone (I
> forget who) was updating MAINTAINERS more generally, so I think he's
> taking care of it. But yes, that sgi address won't work.
>
> Me: It sounds like you are still interested in being the main Web Page
> maintainer for GDB. Is that true?
>
> Jim Kingdon: No. I haven't edited a GDB web page in many years, and
> don't expect to in the future.
As you can see from the patch, I am volunteering to take Jim's place.
(With as little on-the-job training from you as possible 8-)
[-- Attachment #2: rsync.patch --]
[-- Type: text/x-patch, Size: 1248 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 3 Feb 2006 22:25:30 -0000
@@ -148,6 +148,22 @@
<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 is
+available for that purpose. Here is how to get a copy of the
+repository, or to synchronize an existing one:
+
+<pre>
+ rsync -az --delete --exclude '#cvs.*' --exclude 'CVSROOT/config' --exclude 'CVSROOT/history' --exclude 'CVSROOT/updatelog' rsync://sources.redhat.com/gdb-cvs gdb-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 +276,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-02-03.</p>
</address>
</body>
[-- Attachment #3: maintainers.patch --]
[-- Type: text/x-patch, Size: 712 bytes --]
2006-02-03 Paul Gilliam <pgilliam@us.ibm.com>
* MAINTAINERS: Take Jim Kingdon's place as lead web pages maintainer.
Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/gdb/MAINTAINERS,v
retrieving revision 1.336
diff -a -u -r1.336 MAINTAINERS
--- MAINTAINERS 20 Jan 2006 22:31:07 -0000 1.336
+++ MAINTAINERS 3 Feb 2006 22:49:05 -0000
@@ -426,8 +426,8 @@
gdb/gdbserver Daniel Jacobowitz dan@debian.org
-Web pages. Jim Kingdon jkingdon@engr.sgi.com ++
- (anyone can edit; kingdon is just lead maintainer)
+Web pages. Paul Gilliam pgilliam@us.ibm.com
+ (anyone can edit; gilliam is just lead maintainer)
Makefile.in, configure* ALL
next prev parent reply other threads:[~2006-02-03 22:58 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
2006-02-01 23:43 ` Daniel Jacobowitz
2006-02-03 22:58 ` PAUL GILLIAM [this message]
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=1139007553.1423.133.camel@dufur.beaverton.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.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