From: Dan Nicolaescu <dann@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: rename and clean unexec.c
Date: Thu, 29 Jul 2010 14:19:21 -0400 [thread overview]
Message-ID: <yxqbp9q40d2.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <834oficgpf.fsf@gnu.org> (Eli Zaretskii's message of "Thu\, 29 Jul 2010 20\:59\:08 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: ofv@wanadoo.es, emacs-devel@gnu.org
>> From: Dan Nicolaescu <dann@gnu.org>
>> Date: Wed, 28 Jul 2010 23:21:40 -0400
>>
>> > Why is it so important to rename this file?
>>
>> For long term maintainability.
>> Good, suggestive file names are good for maintainability.
>
> But we've been living with this file, in parallel with other unex*,
> for ages. Why is it suddenly a problem now? What changed?
This file was used before by other platforms that we've removed support for.
It is now used by a single platform.
Before we did not rename files because CVS could not do it right.
I've worked very hard at removing decades of accumulated cruft, please
don't stand in the way for no good reason.
next prev parent reply other threads:[~2010-07-29 18:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 4:38 rename and clean unexec.c Dan Nicolaescu
2010-07-28 17:45 ` Eli Zaretskii
2010-07-28 19:46 ` Dan Nicolaescu
2010-07-28 20:13 ` Óscar Fuentes
2010-07-28 20:53 ` Eli Zaretskii
2010-07-28 22:55 ` Dan Nicolaescu
2010-07-29 3:06 ` Eli Zaretskii
2010-07-29 3:21 ` Dan Nicolaescu
2010-07-29 17:59 ` Eli Zaretskii
2010-07-29 18:09 ` Óscar Fuentes
2010-07-29 18:19 ` Dan Nicolaescu [this message]
2010-07-29 20:37 ` Eli Zaretskii
2010-07-29 21:18 ` Dan Nicolaescu
2010-07-30 6:39 ` Eli Zaretskii
2010-07-30 7:37 ` Dan Nicolaescu
2010-07-30 9:30 ` Eli Zaretskii
2010-08-04 16:40 ` Dan Nicolaescu
2010-08-04 16:55 ` Óscar Fuentes
2010-08-04 17:38 ` Eli Zaretskii
2010-08-04 21:58 ` Óscar Fuentes
2010-08-05 3:07 ` Eli Zaretskii
2010-07-30 9:12 ` Stefan Monnier
2010-08-05 17:27 ` Eli Zaretskii
2010-08-05 18:41 ` Dan Nicolaescu
2010-08-05 21:38 ` Stefan Monnier
2010-07-29 7:54 ` Andreas Schwab
2010-07-28 20:46 ` Eli Zaretskii
2010-08-05 17:31 ` Eli Zaretskii
2010-08-05 18:46 ` Dan Nicolaescu
2010-08-05 21:39 ` Stefan Monnier
2010-08-13 11:19 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yxqbp9q40d2.fsf@fencepost.gnu.org \
--to=dann@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).