From: Eli Zaretskii <eliz@gnu.org>
To: Thiago Jung Bauermann <thiago.bauermann@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Rename python files.
Date: Fri, 14 Aug 2009 10:33:00 -0000 [thread overview]
Message-ID: <83eirekgy2.fsf@gnu.org> (raw)
In-Reply-To: <200908132359.32327.thiago.bauermann@gmail.com>
> From: Thiago Jung Bauermann <thiago.bauermann@gmail.com>
> Date: Thu, 13 Aug 2009 23:59:31 -0300
>
> Eli asked that the source code and testcase files pertaining to python
> scripting support be renamed in order to support the 8.3 limitation in DOS. I
> don't like the fnchange.lst solution because it's just one more arcane thing
> we would have to know in order to hack GDB. So I prefer straight renaming of
> the files.
Thanks. I prefer renaming also, especially for files that (I hope)
will be compiled in the DJGPP port of GDB. fnchange.lst is the last
resort, and using it is tricky for files that are actually compiled.
> How should said renaming be done, by submitting and committing a patch which
> removes the old file and adds a new one, or by moving things around in CVSROOT?
The latter is better, because it preserves the CVS history. But I
think it requires special privileges on the repository.
next prev parent reply other threads:[~2009-08-14 7:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 7:12 Thiago Jung Bauermann
2009-08-14 10:33 ` Eli Zaretskii [this message]
2009-08-25 15:29 ` Matt Rice
2009-08-29 16:59 ` Thiago Jung Bauermann
2009-08-29 18:01 ` Matt Rice
2009-08-25 17:11 ` Andreas Schwab
2009-09-03 22:27 ` Joel Brobecker
2009-09-07 0:48 ` Thiago Jung Bauermann
2009-09-07 21:43 ` Joel Brobecker
2009-09-09 17:47 ` 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=83eirekgy2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=thiago.bauermann@gmail.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