Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Jim Meyering <meyering@redhat.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: ping: Re: [rfa] git repo fixup: delete gdb/testsuite/gdb.gdbtk
Date: Sat, 11 Dec 2010 05:29:00 -0000	[thread overview]
Message-ID: <20101211052850.GA17949@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3lj4ti3i5.fsf@fleche.redhat.com>

ping

On Tue, 16 Nov 2010 18:26:26 +0100, Tom Tromey wrote:
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

make[5]: Entering directory `.../gdb/testsuite/gdb.gdbtk'
make[5]: *** No rule to make target `clean'.  Stop.

> Jan> therefore I would like to delete:
> Jan> gdb/testsuite/gdb.gdbtk
> Jan> gdb/testsuite/gdb.gdbtk/ChangeLog
> Jan> gdb/testsuite/gdb.gdbtk/browser.exp
> Jan> gdb/testsuite/gdb.gdbtk/c_variable.exp
> Jan> gdb/testsuite/gdb.gdbtk/console.exp
> Jan> gdb/testsuite/gdb.gdbtk/cpp_variable.exp
> Jan> gdb/testsuite/gdb.gdbtk/srcwin.exp
> Jan> gdb/testsuite/gdb.gdbtk/windows.exp
> 
> Jan> so that `make clean' succeeds like in the CVS checkout.
> Jan> IIRC I/everyone have to rights to push it for "master".
> 
> Jan> Are there any issues?
> 
> I don't know.  I've CC'd Jim Meyering, who maintains the git mirroring.
> 
> Jim, these are files that are part of the Insight module in CVS.  They
> shouldn't be in gdb.git.  Can we just delete them?  Or do we need
> something different?
> 
> Tom


  reply	other threads:[~2010-12-11  5:29 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   ` Jan Kratochvil [this message]
2011-02-21 19:39     ` ping2: " Jan Kratochvil
2011-02-21 19:48       ` Jim Meyering
2011-02-21 22:23         ` Jan Kratochvil

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=20101211052850.GA17949@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=meyering@redhat.com \
    --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