all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: ulf.jasper@web.de, emacs-devel@gnu.org
Subject: Re: newsticker-*.el files
Date: Mon, 09 Jun 2008 11:06:24 +0300	[thread overview]
Message-ID: <ufxrnkp6n.fsf@gnu.org> (raw)
In-Reply-To: <200806082201.m58M142d000380@sallyv1.ics.uci.edu>

> From: Dan Nicolaescu <dann@ics.uci.edu>
> Cc: Ulf Jasper <ulf.jasper@web.de>, emacs-devel@gnu.org
> Date: Sun, 08 Jun 2008 15:01:04 -0700
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
>   > The newly installed newsticker-*.el files cause file-name clashes on
>   > 8+3 (a.k.a. DOS) filesystems.  Can we rename them in a way that avoids
>   > such clashes?  All that is needed that the first 8 characters of the
>   > basename be different; as long as they are, there's no problem for the
>   > basename itself to be longer than 8 characters.
> 
> The DOS port currently does not work, it has been approved for removal,
> and you said that it might never be revived.
> 
> Why do this work now, when it's highly possible that the uglyfied names
> might never be needed?  
> 
> Why not do the renaming work at the time when the DOS platform is
> brought back to life?

Why ask these questions time and again, when I already answered them
several times in the past?  Here goes again: I'm asking not to make my
life harder if and when I find time to make the DOS port of Emacs 23
work again.  Doing all of the renames later will make it much harder,
especially since CVS doesn't cope well with renaming; doing it now
doesn't lose any CVS history, and doesn't require contacting all of
the package maintainers at once.

The author agreed (in private email to me) to rename the files when he
has time.  I trust him that the names he comes up with will not be
ugly, because it's his package.  So it's a non-issue, and making it an
issue each time this comes up only eats up more of our resources than
is necessary.

If you indeed cherish so much our resources, why waste them on this
subject time and again?  It almost sounds like you have an agenda
here.  Do you?





  parent reply	other threads:[~2008-06-09  8:06 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-08 18:22 newsticker-*.el files Eli Zaretskii
2008-06-08 22:01 ` Dan Nicolaescu
2008-06-08 23:44   ` David De La Harpe Golden
2008-06-09  8:13     ` Eli Zaretskii
2008-06-09  8:21       ` Miles Bader
2008-06-09  9:33         ` Juanma Barranquero
2008-06-08 23:44   ` Leo
2008-06-09  8:16     ` Eli Zaretskii
2008-06-09  8:23       ` Miles Bader
2008-06-09  9:12         ` Eli Zaretskii
2008-06-09  9:34           ` David Kastrup
2008-06-09  9:56             ` Juanma Barranquero
2008-06-09 23:15             ` Richard M Stallman
2008-06-09 23:45               ` Miles Bader
2008-06-10  3:25                 ` dhruva
2008-06-10 17:33                 ` Richard M Stallman
2008-06-09 17:22       ` Richard M Stallman
2008-06-09  0:30   ` Miles Bader
2008-06-09  1:49   ` Stefan Monnier
2008-06-09  8:23     ` Eli Zaretskii
2008-06-09 12:43       ` Dan Nicolaescu
2008-06-09 12:47         ` David Kastrup
2008-06-09 14:25           ` Eli Zaretskii
2008-06-09  8:06   ` Eli Zaretskii [this message]
2008-06-09  8:13     ` Miles Bader
2008-06-09  9:09       ` Eli Zaretskii
2008-06-09 13:35     ` Chong Yidong
     [not found] ` <84bq2beol7.fsf@web.de>
2008-06-09 17:52   ` Ulf Jasper
2008-06-09 18:19     ` Chong Yidong
2008-06-09 18:39       ` David Kastrup
2008-06-09 19:38         ` Ulf Jasper
2008-06-10  7:27     ` Thien-Thi Nguyen
2008-06-10 18:34       ` Ulf Jasper
2008-06-10 20:10         ` Eli Zaretskii
2008-06-11  8:06         ` Thien-Thi Nguyen
2008-06-12 19:05           ` Ulf Jasper
2008-06-12 19:52             ` Stefan Monnier
2008-06-12 20:30               ` Ulf Jasper
2008-06-13  8:23             ` Thien-Thi Nguyen

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=ufxrnkp6n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=ulf.jasper@web.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.