From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: cyd@stupidchicken.com, bug-gnulib@gnu.org,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Files from gnulib
Date: Wed, 26 Jan 2011 00:06:19 +0200 [thread overview]
Message-ID: <83ipxcy6xw.fsf@gnu.org> (raw)
In-Reply-To: <4D3F3F7B.40402@cs.ucla.edu>
> Date: Tue, 25 Jan 2011 13:24:11 -0800
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: cyd@stupidchicken.com, bug-gnulib@gnu.org, monnier@iro.umontreal.ca,
> emacs-devel@gnu.org
>
> On 01/25/11 11:02, Eli Zaretskii wrote:
>
> > To read the instructions, you need to unpack the archive first.
>
> That may have been true years ago, when the tarballs themselves were
> the main way that one could find out how to do maintenance. But that
> long ago stopped being true for Emacs. If I wanted to come up to
> speed on how to build Emacs for MS-DOS, the first thing I'd do would
> be a Google search, which would point me at places like
> <http://www.emacswiki.org/emacs-fr/EmacsForDOS> and
> <http://www.gnu.org/software/emacs/manual/html_node/emacs/MS_002dDOS.html>.
> If these places contain extraction instructions, that's good enough.
And what about the emacs-25.chg file? Would you expect users to
google for it as well, and copy-paste it into their shell window? I
hope you will agree that it's a very bad idea. So the file will have
to be extracted first, and you are back at the same problem as with
the instructions again.
> For example, it should be pretty easy to check emacs-25.chg
> automatically; is that done with GDB?
Yes, it is done. But it doesn't catch all the errors. More
importantly, the remapping file is maintained manually. See my
response to Stefan.
> > If the decision is not to rename these few files in the Emacs
> > distribution, and instead ask me to cope with these complications, I
> > will understand that the knee-jerk reaction of too many members of
> > this community when they hear "MS-DOS" is more important that any
> > voice of reason
>
> I hope that you don't include me in members whose knees are jerking.
I no longer know who is and who isn't. Oscar's was the only message
that sounded like a glimpse of light in the darkness.
> Personally I would just rename the files in gnulib and be done with
> it, as none of the name changes seem to be onerous. However, we don't
> seem to have consensus for that now; I seem to be the only gnulib
> developer who would go that route.
We are talking about renaming files in the Emacs repo. Why would
gnulib developers have any say in that?
> Also, the problem of non-8+3 file names does not seem to be limited
> to gnulib-derived files.
Yes, they are limited to gnulib-derived files. If you mean Org, I'm
sure those files will be renamed.
> All in all it sounds like automating the renaming on the MS-DOS side
> would be a reasonable thing to do.
Theoretically, yes. It sounded like that years ago, when it was
introduced into GDB. I feel much better now, thank you.
> This is a bit of work but doesn't seem that hard. And if we get the
> automation working well with Emacs we could then apply similar ideas
> to GDB as well, and make GDB development less error-prone on MS-DOS.
Who is "we" here, I wonder.
next prev parent reply other threads:[~2011-01-25 22:06 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 12:15 Files from gnulib Eli Zaretskii
2011-01-23 12:40 ` Eli Zaretskii
2011-01-23 19:29 ` Paul Eggert
2011-01-23 22:16 ` Bruno Haible
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 11:32 ` Bastien ROUCARIES
2011-01-25 14:07 ` 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
2011-01-26 16:11 ` Files from gnulib Stefan Monnier
2011-01-26 4:02 ` Eli Zaretskii
2011-01-26 0:32 ` Jason Rumney
2011-01-26 3:12 ` Stefan Monnier
2011-01-25 21:24 ` Paul Eggert
2011-01-25 22:06 ` Eli Zaretskii [this message]
2011-01-26 0:54 ` Paul Eggert
2011-01-26 4:10 ` Eli Zaretskii
2011-01-26 11:13 ` Jim Meyering
2011-01-26 13:09 ` Eli Zaretskii
2011-01-26 13:23 ` Jim Meyering
2011-01-26 13:29 ` Lennart Borgman
2011-01-26 13:33 ` Eli Zaretskii
2011-01-26 13:37 ` Eli Zaretskii
2011-01-26 13:50 ` Jim Meyering
2011-01-26 12:27 ` Andreas Schwab
2011-01-26 13:17 ` Eli Zaretskii
2011-01-26 13:24 ` Andreas Schwab
2011-01-26 13:41 ` Eli Zaretskii
2011-01-27 8:32 ` Paul Eggert
2011-01-27 11:08 ` Eli Zaretskii
2011-01-28 7:30 ` Paul Eggert
2011-01-28 14:20 ` Eli Zaretskii
2011-01-31 9:29 ` Compartmentalizing the 8.3 problem into the msdos directory Paul Eggert
2011-02-05 10:59 ` Eli Zaretskii
2011-02-05 11:20 ` Paul Eggert
2011-02-05 11:26 ` Eli Zaretskii
2011-02-05 23:30 ` Paul Eggert
2011-02-06 0:55 ` Glenn Morris
2011-02-06 13:37 ` Miles Bader
2011-02-06 4:01 ` Eli Zaretskii
2011-02-06 7:30 ` Paul Eggert
2011-02-06 9:59 ` Eli Zaretskii
2011-01-24 7:57 ` Files from gnulib Glenn Morris
2011-01-24 16:37 ` Stefan Monnier
2011-01-24 4:07 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2011-01-25 8:20 RE : " Bastien ROUCARIES
2011-01-25 14:05 ` Eli Zaretskii
2011-01-25 14:51 ` Jim Meyering
2011-01-25 15:33 ` Eli Zaretskii
2011-01-25 16:50 ` Ulrich Mueller
2011-01-25 18:50 ` Eli Zaretskii
2011-01-25 19:31 ` Ulrich Mueller
2011-01-25 19:38 ` Eli Zaretskii
2011-01-25 20:00 ` Ulrich Mueller
2011-01-25 20:09 ` Eli Zaretskii
2011-01-25 19:52 ` Óscar Fuentes
2011-01-25 20:19 ` Eli Zaretskii
2011-01-25 19:04 ` Stefan Monnier
2011-01-25 19:36 ` Eli Zaretskii
2011-01-25 22:37 ` Bastien ROUCARIES
2011-01-26 3:49 ` Eli Zaretskii
2011-01-26 11:02 ` Jim Meyering
2011-01-26 11:52 ` Bastien ROUCARIES
2011-01-26 11:58 ` Bastien ROUCARIES
2011-01-26 13:12 ` Eli Zaretskii
2011-01-26 12:52 ` Eli Zaretskii
2011-01-26 13:33 ` Bastien ROUCARIES
2011-01-26 13:48 ` Eli Zaretskii
2011-01-26 15:26 ` Bastien ROUCARIES
2011-01-26 15:46 ` Eli Zaretskii
2011-01-26 15:57 ` Bastien ROUCARIES
2011-01-26 18:56 ` Eli Zaretskii
2011-01-26 14:35 ` Andy Moreton
2011-01-26 15:31 ` Bastien ROUCARIES
2011-01-26 18:28 ` Miles Bader
2011-01-26 18:59 ` Eli Zaretskii
2011-01-27 10:54 ` Simon Josefsson
2011-01-28 2:27 ` Paul Eggert
2012-08-23 11:36 ` Bastien ROUCARIES
2012-08-23 16:23 ` 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=83ipxcy6xw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bug-gnulib@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--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).