From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'H.J. Lu'" <hjl.tools@gmail.com>, <meyering@redhat.com>
Cc: "'GDB'" <gdb@sourceware.org>
Subject: RE: gdb.git mirror is broken
Date: Tue, 06 Oct 2009 06:23:00 -0000 [thread overview]
Message-ID: <001501ca464d$90ad40e0$b207c2a0$@u-strasbg.fr> (raw)
In-Reply-To: <6dc9ffc80910051730p207a14f2m5ee6ff560ea60c33@mail.gmail.com>
This explains the problems
I also get when trying to test my patches
on gcc16.
Pierre Muller
Pascal language support maintainer for GDB
> -----Message d'origine-----
> De : gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] De la
> part de H.J. Lu
> Envoyé : Tuesday, October 06, 2009 2:31 AM
> À : meyering@redhat.com
> Cc : GDB
> Objet : gdb.git mirror is broken
>
> 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.
>
> Thanks.
>
>
> --
> H.J.
next prev parent reply other threads:[~2009-10-06 6:23 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 [this message]
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
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='001501ca464d$90ad40e0$b207c2a0$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=meyering@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