From: Tristan Gingold <gingold@adacore.com>
To: Joel Brobecker <brobecker@adacore.com>, Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: RFA: move *-stub.c to stubs/
Date: Thu, 08 Mar 2012 14:44:00 -0000 [thread overview]
Message-ID: <CDD2588F-46FD-4535-9616-6E1F1D10086E@adacore.com> (raw)
In-Reply-To: <20120305172220.GI2853@adacore.com>
On Mar 5, 2012, at 6:22 PM, Joel Brobecker wrote:
>>> 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.
>>
>>
>> I think git log will understand the rename anyway, so that's fine with me.
>> I can't speak for others, but my only use of cvs log nowadays is through the
>> cvs web frontend.
>
> I prefer this approach as well, as I'd rather we avoid repository
> surgery just for these relatively minor files…
Ok, now committed.
Tristan.
next prev parent reply other threads:[~2012-03-08 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 16:04 Tristan Gingold
2012-03-05 17:16 ` Pedro Alves
2012-03-05 17:22 ` Joel Brobecker
2012-03-08 14:44 ` Tristan Gingold [this message]
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=CDD2588F-46FD-4535-9616-6E1F1D10086E@adacore.com \
--to=gingold@adacore.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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