From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Jim Meyering <jim@meyering.net>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: ping2: Re: [rfa] git repo fixup: delete gdb/testsuite/gdb.gdbtk
Date: Mon, 21 Feb 2011 22:23:00 -0000 [thread overview]
Message-ID: <20110221201409.GA14510@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <877hctch4b.fsf@rho.meyering.net>
Hi Jim,
On Mon, 21 Feb 2011 20:39:00 +0100, Jim Meyering wrote:
> I'll let the regularly scheduled cvs-to-git sync propagate that
> change to the public git repository along with whatever's happened
> in the preceding 30 minutes.
It is now the commit:
commit dd3f1356fc2e6ddae18b8b6546f1917044d69869
Author: Jim Meyering <meyering@redhat.com>
Date: Mon Feb 21 19:33:31 2011 +0000
maint: remove stray Insight files per request:
and I can confirm `make clean' has started working now.
Thanks,
Jan
prev parent reply other threads:[~2011-02-21 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 5:11 Jan Kratochvil
2010-11-16 17:26 ` Tom Tromey
2010-12-11 5:29 ` ping: " Jan Kratochvil
2011-02-21 19:39 ` ping2: " Jan Kratochvil
2011-02-21 19:48 ` Jim Meyering
2011-02-21 22:23 ` Jan Kratochvil [this message]
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=20110221201409.GA14510@host1.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@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