This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: using rsync to create local repository
- From: Daniel Jacobowitz <drow at false dot org>
- To: PAUL GILLIAM <pgilliam at us dot ibm dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Mon, 6 Feb 2006 16:20:21 -0500
- Subject: Re: using rsync to create local repository
- References: <1138301788.1423.54.camel@dufur.beaverton.ibm.com> <20060126190733.GA13020@nevyn.them.org> <1138308820.1423.59.camel@dufur.beaverton.ibm.com> <20060126205524.GA17357@nevyn.them.org> <1138318142.1423.70.camel@dufur.beaverton.ibm.com> <20060201234306.GD14187@nevyn.them.org> <1139007553.1423.133.camel@dufur.beaverton.ibm.com>
On Fri, Feb 03, 2006 at 02:59:13PM -0800, PAUL GILLIAM wrote:
> 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?
Yes. Except, you've now switched back to gdb-cvs, and that's not the
right repository.
> I have also attached a patch to MAINTAINERS in light of the following
> e-mail exchange:
Do we want a maintainer for the web pages right now? A serious
question.
With the recent changes to MAINTAINERS, if there is one, then that
individual needs to review all web page patches, and be interested in
taking general care of the web pages. If there isn't one, any global
maintainer can make changes to the web pages. I have the feeling that
distributing the responsibility, for this particular area, would be
a better choice.
Maybe it wouldn't. I'm open to other opinions.
--
Daniel Jacobowitz
CodeSourcery