Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GDB <gdb@sourceware.org>
Subject: Re: gdb.git mirror is broken
Date: Tue, 06 Oct 2009 06:45:00 -0000	[thread overview]
Message-ID: <878wfp9g10.fsf@meyering.net> (raw)
In-Reply-To: <6dc9ffc80910051730p207a14f2m5ee6ff560ea60c33@mail.gmail.com> 	(H. J. Lu's message of "Mon, 5 Oct 2009 17:30:56 -0700")

H.J. Lu wrote:
> Hi Jim,
>
> gdb.git mirror at
>
> http://sources.redhat.com/git/gdb.git
>
> is broken. The problems are
>
> 1: "cpu" directory is missing.
> 2.  Top level files and gdb/gdbserver, bfd, sim, include directories
> haven't been updated  since 2009-09-16.

Hi H.J.

When I check out gdb using CVS, via this,
(as recommended here http://www.gnu.org/software/gdb/current/)

    cvs -z3 -d :pserver:anoncvs@sourceware.org:/cvs/src co gdb

That created a single directory named "src/", containing no
top level files:

    $ ls src
    CVS/  config/  etc/  include/  libdecnumber/  opcodes/   sim/
    bfd/  cpu/     gdb/  intl/     libiberty/     readline/  texinfo/

This suggests that something is wrong with CVS.

Has someone been changing the modules file that
describes what you get when you check out gdb from CVS?

Is there a better way to checkout from CVS?

Just to confirm, I checked it out again (same exact command, also into
a new empty directory), and this time, I got all of the expected files.

If similar things happen during the mirroring process,
that could well explain the problem.

At first, I suspected the recent changes in my mirroring script
to mirror binutils to git, but for the problem to date
back to Sept 16, I now wonder if it's something else.

I'm investigating...


  parent reply	other threads:[~2009-10-06  6:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06  0:31 H.J. Lu
2009-10-06  6:23 ` Pierre Muller
2009-10-06  6:45 ` Jim Meyering [this message]
2009-10-06  6:51 ` Jim Meyering
2009-10-06  7:38 ` Jim Meyering
2009-10-06 13:08   ` H.J. Lu
2009-10-06 14:07     ` Jim Meyering
2009-10-06 14:26       ` Joseph S. Myers
2009-10-06 14:33         ` Jim Meyering
2009-10-06 16:11           ` Joseph S. Myers
2009-10-07  4:29         ` Matt Rice
2009-10-10  5:35           ` Matt Rice
2009-10-06 16:06       ` Tom Tromey
2009-10-06 16:21         ` Jim Meyering
2009-10-06 15:45   ` Joel Brobecker
2009-10-06 18:38     ` Eli Zaretskii
2009-10-06 19:01       ` Joel Brobecker
2009-10-06 20:36         ` Eli Zaretskii
2009-10-06 21:10           ` Joel Brobecker
2009-10-06 22:04             ` Tom Tromey
2009-10-07  7:29               ` Eli Zaretskii
2009-10-07  7:27             ` Eli Zaretskii
2009-10-06 16:08   ` Tom Tromey
2009-10-06 16:09     ` Jim Meyering

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=878wfp9g10.fsf@meyering.net \
    --to=jim@meyering.net \
    --cc=gdb@sourceware.org \
    --cc=hjl.tools@gmail.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