Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: PAUL GILLIAM <pgilliam@us.ibm.com>
To: overseers@soruces.redhat.com, gdb@sources.redhat.com
Subject: using rsync to create local repository
Date: Thu, 26 Jan 2006 19:07:00 -0000	[thread overview]
Message-ID: <1138301788.1423.54.camel@dufur.beaverton.ibm.com> (raw)

Hi,

In order to use Janus Johnson's cool binary patch finder, I need to
create a local copy of GDB's cvs repository.

Her patch finder does a binary search through the patches find the one
that breaks or fixes what you are interested in.  For each patch
examined, a source tree is updated, the project is built and a test
script is run to see if whatever is broken or fixed.

Although it's possible to do this with a remote repository, the time
needed for cvs updates (not to mention the network traffic) would be
prohibitory.

For Janus' GCC testing, she uses the following command to create and
update a local copy of the cvs repository:

rsync --archive --delete --compress --progress \
      --exclude '#cvs.*' --exclude 'CVSROOT/config' \
      --exclude 'CVSROOT/history' --exclude 'CVSROOT/updatelog' \
      rsync://gcc.gnu.org/gcc-cvs gcc-cvs

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

But when I tried to do a checkout, I got this:

[pgilliam@dufur test]$ cvs -d /home/pgilliam/gdb/gdb-cvs/ co gdb
cvs checkout: module `naked-gdb' in modules file contains infinite loop
cvs checkout: module `naked-gdb' in modules file contains infinite loop
cvs checkout: module `naked-texinfo' in modules file contains infinite
loop
cvs checkout: module `naked-gdb' in modules file contains infinite loop
cvs checkout: module `naked-texinfo' in modules file contains infinite
loop
cvs checkout: module `naked-bfd' in modules file contains infinite loop
cvs checkout: module `naked-gdb' in modules file contains infinite loop
cvs checkout: module `naked-texinfo' in modules file contains infinite
loop
cvs checkout: module `naked-bfd' in modules file contains infinite loop

... and so on


Any ideas on what I am doing wrong?

Thanks for your help,

-=# Paul Gilliam #=-



             reply	other threads:[~2006-01-26 18:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26 19:07 PAUL GILLIAM [this message]
2006-01-26 20:37 ` Daniel Jacobowitz
2006-01-26 20:55   ` PAUL GILLIAM
2006-01-26 21:03     ` 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=1138301788.1423.54.camel@dufur.beaverton.ibm.com \
    --to=pgilliam@us.ibm.com \
    --cc=gdb@sources.redhat.com \
    --cc=overseers@soruces.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