From: Tristan Gingold <gingold@adacore.com>
To: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: RFA: move *-stub.c to stubs/
Date: Mon, 05 Mar 2012 16:04:00 -0000 [thread overview]
Message-ID: <BC462D69-603A-4A3D-ABD1-850839E9A6EB@adacore.com> (raw)
Hi,
now that a stubs/ subdirectory has been created, I propose to move existing stub files to it.
No diff created, no regression tests executed.
Should I simply cvs remove/cvs add ? We will loose the cvs log, but for i386-stub.c (the only one I checked), it is not very long.
Tristan.
gdb/
2012-03-05 Tristan Gingold <gingold@adacore.com>
* sparc-stub.c: Move to stubs/
* sh-stub.c: Likewise.
* m68k-stub.c: Likewise.
* m32r-stub.c: Likewise.
* i386-stub.c: Likewise.
gdb/stubs/
2012-03-05 Tristan Gingold <gingold@adacore.com>
* sparc-stub.c: Move from ..
* sh-stub.c: Likewise.
* m68k-stub.c: Likewise.
* m32r-stub.c: Likewise.
* i386-stub.c: Likewise.
next reply other threads:[~2012-03-05 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 16:04 Tristan Gingold [this message]
2012-03-05 17:16 ` Pedro Alves
2012-03-05 17:22 ` Joel Brobecker
2012-03-08 14:44 ` Tristan Gingold
2012-03-12 22:30 ` Stan Shebs
2012-03-12 23:04 ` Joel Brobecker
2012-03-12 23:15 ` Pedro Alves
2012-03-13 0:35 ` Joel Brobecker
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=BC462D69-603A-4A3D-ABD1-850839E9A6EB@adacore.com \
--to=gingold@adacore.com \
--cc=gdb-patches@sourceware.org \
/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