From: Jim Meyering <jim@meyering.net>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
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 19:48:00 -0000 [thread overview]
Message-ID: <877hctch4b.fsf@rho.meyering.net> (raw)
In-Reply-To: <20110221185841.GA3082@host1.dyn.jankratochvil.net> (Jan Kratochvil's message of "Mon, 21 Feb 2011 19:58:41 +0100")
Jan Kratochvil wrote:
> ping
>
> On Sat, 11 Dec 2010 06:28:50 +0100, Jan Kratochvil wrote:
> 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?
Hi Jan,
This is something I have to do. Sorry I didn't respond sooner.
For the record, I've done the following in an empty directory:
----------------------
git clone ~/mirror-git-to-cvs/repo/src
cd src && rm -rf gdb/testsuite/gdb.gdbtk
cat <<\EOF > msg
maint: remove stray Insight files per request:
See this thread for details:
http://thread.gmane.org/gmane.comp.gdb.patches/61489/focus=63536
* gdb/testsuite/gdb.gdbtk/ChangeLog: Remove file.
* gdb/testsuite/gdb.gdbtk/browser.exp: Likewise.
* gdb/testsuite/gdb.gdbtk/c_variable.exp: Likewise.
* gdb/testsuite/gdb.gdbtk/console.exp: Likewise.
* gdb/testsuite/gdb.gdbtk/cpp_variable.exp: Likewise.
* gdb/testsuite/gdb.gdbtk/srcwin.exp: Likewise.
* gdb/testsuite/gdb.gdbtk/windows.exp: Likewise.
EOF
git ci -Fmsg -a
git push
----------------------
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.
Jim
next prev parent reply other threads:[~2011-02-21 19:39 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 [this message]
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=877hctch4b.fsf@rho.meyering.net \
--to=jim@meyering.net \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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