From: Daniel Jacobowitz <drow@false.org>
To: PAUL GILLIAM <pgilliam@us.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: using rsync to create local repository
Date: Mon, 06 Feb 2006 21:20:00 -0000 [thread overview]
Message-ID: <20060206212021.GA29510@nevyn.them.org> (raw)
In-Reply-To: <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
prev parent reply other threads:[~2006-02-06 21:20 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
2006-02-06 21:20 ` Daniel Jacobowitz [this message]
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=20060206212021.GA29510@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=pgilliam@us.ibm.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