From: Eli Zaretskii <eliz@gnu.org>
To: Jim Meyering <jim@meyering.net>
Cc: eggert@CS.UCLA.EDU, bug-gnulib@gnu.org, bruno@clisp.org,
cyd@stupidchicken.com, emacs-devel@gnu.org,
monnier@IRO.UMontreal.CA, eblake@redhat.com
Subject: Re: Proposed gnulib renames
Date: Wed, 26 Jan 2011 21:15:03 +0200 [thread overview]
Message-ID: <83y667wk7c.fsf@gnu.org> (raw)
In-Reply-To: <87r5bzlce1.fsf@meyering.net>
> From: Jim Meyering <jim@meyering.net>
> Cc: eblake@redhat.com, eggert@CS.UCLA.EDU, bug-gnulib@gnu.org, cyd@stupidchicken.com, emacs-devel@gnu.org, monnier@IRO.UMontreal.CA, bruno@clisp.org
> Date: Wed, 26 Jan 2011 19:59:18 +0100
>
> Requiring doslfn solely for those *building* emacs on DOS would
> allow the names of all C source and other build-only files to be "long".
> To gain that benefit, users would *not* have to install doslfn.
>
> However, to extend that benefit to files loaded by emacs
> at run time, they would.
There's no reason to believe that file-name conflicts will be limited
to C files only. C files in Emacs are added very infrequently, while
Lisp files much more frequently.
next prev parent reply other threads:[~2011-01-26 19:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 15:53 Proposed gnulib renames Eric Blake
2011-01-26 16:08 ` Eric Blake
2011-01-26 16:36 ` Jim Meyering
2011-01-26 18:51 ` Eli Zaretskii
2011-01-26 18:59 ` Jim Meyering
2011-01-26 19:15 ` Eli Zaretskii [this message]
2011-01-26 19:48 ` Jim Meyering
2011-01-27 0:39 ` Paul Eggert
2011-01-27 4:11 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2011-01-23 12:15 Files from gnulib Eli Zaretskii
2011-01-23 19:29 ` Paul Eggert
2011-01-24 3:26 ` Stefan Monnier
2011-01-24 4:01 ` Eli Zaretskii
2011-01-24 23:26 ` Paul Eggert
2011-01-25 4:00 ` Eli Zaretskii
2011-01-25 8:48 ` Paul Eggert
2011-01-25 11:24 ` Eli Zaretskii
2011-01-25 18:07 ` Paul Eggert
2011-01-25 19:02 ` Eli Zaretskii
2011-01-25 21:03 ` Stefan Monnier
2011-01-25 21:54 ` Eli Zaretskii
2011-01-25 22:15 ` Stefan Monnier
2011-01-26 1:05 ` Paul Eggert
2011-01-26 4:12 ` Eli Zaretskii
2011-01-26 6:01 ` Eli Zaretskii
2011-01-26 15:19 ` Proposed gnulib renames [was: Files from gnulib] Eric Blake
2011-01-26 15:58 ` Proposed gnulib renames Eli Zaretskii
2011-01-26 17:33 ` Bruno Haible
2011-01-26 18:40 ` Eli Zaretskii
2011-01-26 19:01 ` Eric Blake
2011-01-26 19:01 ` Bruno Haible
2011-01-26 19:18 ` Eli Zaretskii
2011-01-27 7:37 ` Paul Eggert
2011-01-27 9:57 ` Eli Zaretskii
2011-01-27 9:58 ` Eli Zaretskii
2011-01-27 9:59 ` Bruno Haible
2011-01-28 1:57 ` Paul Eggert
2011-01-27 10:14 ` Bruno Haible
2011-01-27 10:23 ` Bruno Haible
2011-01-28 0:32 ` Paul Eggert
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=83y667wk7c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=eblake@redhat.com \
--cc=eggert@CS.UCLA.EDU \
--cc=emacs-devel@gnu.org \
--cc=jim@meyering.net \
--cc=monnier@IRO.UMontreal.CA \
/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).