unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: bug#5813: remove __DJGPP__ version tests
Date: Fri, 02 Apr 2010 04:35:50 -0400	[thread overview]
Message-ID: <yxqiq8a8d5l.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83oci2wb6i.fsf@gnu.org> (Eli Zaretskii's message of "Fri\, 02 Apr 2010 10\:44\:37 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Cc: 5813-done@debbugs.gnu.org
>> From: Dan Nicolaescu <dann@gnu.org>
>> Date: Thu, 01 Apr 2010 19:26:43 -0400
>> 
>> Can you please also remove comments like:
>> /* Demacs 1.1.1 91/10/16 HIRANO Satoshi */
>> that have about zero use now.
>
> Sorry, no.  Not unless we are removing all the other "personalized"
> comments, of which we have quite a few.  Some examples:
>
>     /* Rewritten for clarity and GC protection by rms in Feb 94.  */
>
>     /* There is no way to specify the before_dot and after_dot
>        operators.  rms says this is ok.  --karl  */
>
>     /* rms, 2003-01-03: I think I have fixed this bug.  */
>
> Personally, I don't like to remove other people's credit, even when
> expressed in this form.  But if we are going to delete all such
> comments, I won't object.

IMHO as long as the personalized comments have some useful information.
/* Demacs 1.1.1 91/10/16 HIRANO Satoshi */ is kind of content free.
[I run into those by chance when searching for -Demacs...]




  reply	other threads:[~2010-04-02  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <yxq634c2snk.fsf@fencepost.gnu.org>
     [not found] ` <8339zfxjyf.fsf@gnu.org>
     [not found]   ` <yxqwrwqn498.fsf@fencepost.gnu.org>
2010-04-02  7:44     ` bug#5813: remove __DJGPP__ version tests Eli Zaretskii
2010-04-02  8:35       ` Dan Nicolaescu [this message]
2010-04-02  8:57         ` 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=yxqiq8a8d5l.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).