From: Jim Meyering <jim@meyering.net>
To: gdb@sourceware.org
Subject: gdb.git hiccup
Date: Sat, 03 Oct 2009 12:30:00 -0000 [thread overview]
Message-ID: <87ws3clkx8.fsf@meyering.net> (raw)
FYI,
In setting up binutils.git, my mirroring script added a bunch of junk to
gdb.git's staging repo (blame the module name that they share, "src"),
and then the regularly-scheduled "sync-from-cvs" pushed a bunch of old
binutils commits and refs to the official gdb.git repo.
Bottom line: gdb.git just got a lot bigger, and at least one ref
(master) is no longer pointing where it should.
If someone can point me to a gdb.git repository I can trust, preferably
already uploaded to sourceware,org, I'll put things back in order.
Sorry for the trouble,
Jim
next reply other threads:[~2009-10-03 12:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 12:30 Jim Meyering [this message]
2009-10-03 13:22 ` Jim Meyering
2009-10-03 15:38 ` Jim Meyering
2009-10-03 17:05 ` Joel Brobecker
2009-10-03 23:35 ` Daniel Jacobowitz
2009-10-04 6:51 ` Jim Meyering
2009-10-04 11:09 ` Frank Ch. Eigler
2009-10-04 12:15 ` Matt Rice
2009-10-04 12:43 ` Jim Meyering
[not found] ` <20091004142139.GA19501@host0.dyn.jankratochvil.net>
2009-10-04 20:16 ` Jim Meyering
2009-10-05 1:46 ` Jan Kratochvil
2009-10-05 10:14 ` Jim Meyering
2009-10-06 20:48 ` Jan Kratochvil
2009-10-06 21:12 ` Jim Meyering
2009-10-06 21:23 ` Jim Meyering
2009-10-04 12:15 ` Jim Meyering
2009-10-04 12:40 ` Frank Ch. Eigler
2009-10-04 14:49 ` Christopher Faylor
2009-10-04 15:05 ` Jim Meyering
2009-10-04 15:15 ` Christopher Faylor
2009-10-04 20:34 ` Jim Meyering
2009-10-06 22:03 ` Joel Brobecker
2009-10-07 14:52 ` Jim Meyering
[not found] ` <20091007192519.GK16338@adacore.com>
2009-10-07 21:13 ` Jim Meyering
2009-10-08 9:20 ` 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=87ws3clkx8.fsf@meyering.net \
--to=jim@meyering.net \
--cc=gdb@sourceware.org \
/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