unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Jacobson <jidanni@dman.ddts.net>
Subject: Re: add-change-log-entry and add-log-mailing-address
Date: Tue, 15 Apr 2003 04:34:21 +0800	[thread overview]
Message-ID: <8765pges36.fsf@jidanni.org> (raw)
In-Reply-To: x53cklvcra.fsf@lola.goethe.zz

>>>>> "D" == David Kastrup <dak@gnu.org> writes:

D> Richard Stallman <rms@gnu.org> writes:
>> Say, why are you guys still emphasizing fuddy duddy mail
>> addresses when like for 10 years now we can go to the person's
>> web page, which of course will mention his mail address.
>> 
>> Finding the email address in the web page is not reliable, and not
>> automatic.  So we will continue using email addresses in change
>> logs.

[Neat, SuperCite put my words in Richard's mouth without even a trace of
difference in this instance.]

D> I don't even have a web page.

My next of kin has a web page but no email address. Now what?

Hmm, I bet if we check the logs, 20 years ago you guys were defending
putting telephone numbers while we were pushing email addresses.

Anyway, I'm all about choice. So, I was just humbly mentioning that
the subject of "what to do if I want my web page's address there
instead of (or even in addition to) my email address" should be
mentioned in the docs.

And, lets say I went on a sudden vacation.  With just my email address, you
would mail into a black hole.  With my web page address, you could
wistfully enjoy my pages until I got back.

Or, let's say I want to ask a VIP a FAQ. Would I want to display my
inadeptness so early in the game by emailing him?  No, I would go to
the FAQ page right there on his web page.

Anyways, the docs should mention what to do, in case it is a better
solution for some users.  I mean the docs shouldn't just assume that
all users want email addresses instead of webpages.

How about users like "IBM".  Would IBM like folks to know a email
address instead of a webpage?

How about users unable to come to grips with spam, and are paranoid
about leaving email addresses around, or switch regularly, but on the
other hand have a healthy web page... the docs should mention what to
do in their case.
-- 
http://jidanni.org/ Taiwan(04)25854780

  reply	other threads:[~2003-04-14 20:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09 19:13 add-change-log-entry and add-log-mailing-address Morten Welinder
2003-04-09 22:25 ` Thien-Thi Nguyen
2003-04-10 22:47 ` Richard Stallman
2003-04-11 23:37   ` Dan Jacobson
2003-04-14  2:36     ` Richard Stallman
     [not found]     ` <mailman.4534.1050287861.21513.bug-gnu-emacs@gnu.org>
2003-04-14  6:01       ` David Kastrup
2003-04-14 20:34         ` Dan Jacobson [this message]
2003-04-15  9:05           ` Alfred M. Szmidt
2003-04-16  3:12             ` Dan Jacobson
     [not found]         ` <mailman.4613.1050363127.21513.bug-gnu-emacs@gnu.org>
2003-04-15 15:08           ` Kevin Rodgers
2003-04-14 12:41     ` Alfred M. Szmidt

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=8765pges36.fsf@jidanni.org \
    --to=jidanni@dman.ddts.net \
    /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).