Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Matt Rice <ratmice@gmail.com>
To: Jim Meyering <jim@meyering.net>
Cc: gdb@sourceware.org
Subject: Re: gdb.git hiccup
Date: Sun, 04 Oct 2009 12:15:00 -0000	[thread overview]
Message-ID: <8ba6bed40910040515t775d36adhaf0c912a43e77bad@mail.gmail.com> (raw)
In-Reply-To: <20091004110911.GI32049@redhat.com>

On Sun, Oct 4, 2009 at 4:09 AM, Frank Ch. Eigler <fche@redhat.com> wrote:
> Hi -
>
> On Sun, Oct 04, 2009 at 08:51:32AM +0200, Jim Meyering wrote:
>> [...]
>> But when I tried to diagnose it, I discovered that there are unreadable
>> temporary pack files owned by from back in February that prevent a local clone.
>>
>>   sourceware$ cd /git/archer.git/objects; ls -l tmp*
>>   -rw-------  1 rmoseley archer  368640 Feb  9  2009 tmp_pack_hMUtoO
>>   -rw-------  1 rmoseley archer  876544 Feb  9  2009 tmp_pack_jmBcho
>>   -rw-------  1 rmoseley archer 1007616 Feb  9  2009 tmp_pack_zbwx0m
>> [...]
>
> These have been zapped.

unfortunately it still isn't working, I think here is what happened

http://sources.redhat.com/git/gitweb.cgi?p=gdb.git;a=commitdiff;h=d1ea5a6d98

from this email (about the win32-termcap.c -> windows-termcap.c rename)

http://sourceware.org/ml/archer/2009-q1/msg00349.html

If archer.git was cloned using --reference or --shared pointing to the
gdb.git repository the archer.git
repository is probably referencing that commit which is no longer
contained in the gdb.git

also, gdb.git currently is missing the windows-termcap.c file, so
wouldn't build on windows

(so we need to make sure the releases are made from cvs not git atm,
just mention this since Joel mentions he's been using git).


  parent reply	other threads:[~2009-10-04 12:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-03 12:30 Jim Meyering
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           ` Jim Meyering
2009-10-04 12:40             ` Frank Ch. Eigler
2009-10-04 12:15           ` Matt Rice [this message]
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 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=8ba6bed40910040515t775d36adhaf0c912a43e77bad@mail.gmail.com \
    --to=ratmice@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=jim@meyering.net \
    /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