Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jim Meyering <jim@meyering.net>
Cc: Tom Tromey <tromey@redhat.com>, GDB <gdb@sourceware.org>
Subject: Re: gdb.git mirror is broken
Date: Tue, 06 Oct 2009 13:08:00 -0000	[thread overview]
Message-ID: <6dc9ffc80910060608u60ccf9eal72ab51f216b7f75c@mail.gmail.com> (raw)
In-Reply-To: <87ws397z1b.fsf@meyering.net>

On Tue, Oct 6, 2009 at 12:38 AM, Jim Meyering <jim@meyering.net> wrote:
> 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.
>
> Considering cpu/ has never been included in a gdb.git mirror
> (it's been explicitly excluded from the beginning), it may
> make sense to reconvert the repository from scratch, in order
> to include that directory and all of its history.
>
> However, that would have the disadvantage of changing all
> existing SHA1 commit values -- which might cause problems with
> the likes of archer.git.

I didn't realize that cpu was excluded on purpose. I just
did a comparison between gdb tree checked out from CVS
and gdb tree checked out from git. I don't mind leaving it as is.

>> 2.  Top level files and gdb/gdbserver, bfd, sim, include directories
>> haven't been updated  since 2009-09-16.
>
> I don't know what caused the process to stop mirroring
> those directories.  It could be a bug in cvsps, git-cvsimport,
> my script, git-push, or even rsync.
>
> IMHO, the best would be to remove CVS from the loop.
> Leading up to that, I propose the following:
>
>  I will re-convert all of gdb's CVS history to git (using parsecvs),
>  not excluding the cpu/ directory this time.  Then, I will add checks
>  to my mirroring script to notify me if git and CVS checkouts ever
>  diverge.

I am enclosing my script at the end of this email. It diffs
all ChangLogs between 2 gdb trees.

> Note that the initial conversion is via parsecvs,
> yet incrementals are via my scripts, which rely on git-cvsimport
> (which in turn relies on cvsps).
>
> If anyone is interested in switching primary GDB development
> to git, once such a new repository is in place and deemed stable,
> I urge you to dump CVS.  While the conversion tools are not always
> reliable, I can assure you that git itself has been amazingly reliable
> for years.
>

It sounds a good idea. But don't we need to switch src tree to git, not
just gdb tree? I don't mind checking out the whole src tree. But we
need a way to build only gcc, gdb, binutils, .... even though there are
more packages.

Thanks.

-- 
H.J.
---
#! /bin/sh

gdb=$1

cl="
./etc/ChangeLog
./gdb/gdbserver/ChangeLog
./gdb/ChangeLog
./gdb/testsuite/ChangeLog
./gdb/doc/ChangeLog
./intl/ChangeLog
./bfd/ChangeLog
./bfd/doc/ChangeLog
./libdecnumber/ChangeLog
./readline/examples/rlfe/ChangeLog
./ChangeLog
./opcodes/ChangeLog
./libiberty/ChangeLog
./config/ChangeLog
./cpu/ChangeLog
./sim/frv/ChangeLog
./sim/arm/ChangeLog
./sim/mcore/ChangeLog
./sim/m32r/ChangeLog
./sim/mips/ChangeLog
./sim/d10v/ChangeLog
./sim/cr16/ChangeLog
./sim/h8300/ChangeLog
./sim/ChangeLog
./sim/sh/ChangeLog
./sim/m68hc11/ChangeLog
./sim/testsuite/frv-elf/ChangeLog
./sim/testsuite/mips64el-elf/ChangeLog
./sim/testsuite/d10v-elf/ChangeLog
./sim/testsuite/ChangeLog
./sim/testsuite/sim/mips/ChangeLog
./sim/testsuite/sim/cr16/ChangeLog
./sim/testsuite/sim/h8300/ChangeLog
./sim/testsuite/sim/sh/ChangeLog
./sim/testsuite/sim/sh64/ChangeLog
./sim/testsuite/sim/sh64/media/ChangeLog
./sim/testsuite/sim/sh64/compact/ChangeLog
./sim/testsuite/m32r-elf/ChangeLog
./sim/igen/ChangeLog
./sim/iq2000/ChangeLog
./sim/ppc/ChangeLog
./sim/v850/ChangeLog
./sim/mn10300/ChangeLog
./sim/sh64/ChangeLog
./sim/erc32/ChangeLog
./sim/common/ChangeLog
./sim/m32c/ChangeLog
./include/gdb/ChangeLog
./include/elf/ChangeLog
./include/opcode/ChangeLog
./include/coff/ChangeLog
./include/aout/ChangeLog
./include/ChangeLog
./include/nlm/ChangeLog
"

for f in $cl
do
  diff -up $f $gdb/$f
done


  reply	other threads:[~2009-10-06 13:08 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
2009-10-06  6:51 ` Jim Meyering
2009-10-06  7:38 ` Jim Meyering
2009-10-06 13:08   ` H.J. Lu [this message]
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=6dc9ffc80910060608u60ccf9eal72ab51f216b7f75c@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=jim@meyering.net \
    --cc=tromey@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