unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: johnw@newartisans.com, emacs-devel@gnu.org,
	monnier@iro.umontreal.ca, rgm@gnu.org, carsten.dominik@gmail.com
Subject: Re: recent changes to org files
Date: Tue, 23 Oct 2007 22:50:14 -0400	[thread overview]
Message-ID: <E1IkWJy-0001GS-Fs@fencepost.gnu.org> (raw)
In-Reply-To: <f7ccd24b0710230449w753f2044s8f6a874e25a1d71@mail.gmail.com> (lekktu@gmail.com)

    Changing next-line to forward-line would *not* be such a kind of
    change, were not for the fact that, in this specific case, it was a
    mistake. A pretty small one.

Someone was trying to get rid of uses of `next-line' in Emacs Lisp
programs.  He made a mistake in the process, something we all do.

However, changing org-mode along with lots of other programs is not
generally wrong.  When there is a general change in conventions, or a
general maintenance activity like "Let's get rid all those compiler
warnings", it would be ridiculous to ask the maintainer of every
package about some tiny change.  We could not get these general
changes done, if we had to do that.

  reply	other threads:[~2007-10-24  2:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 22:28 recent changes to org files Glenn Morris
2007-10-22 22:57 ` John Wiegley
2007-10-23  0:57   ` Stefan Monnier
2007-10-23  9:18     ` Carsten Dominik
2007-10-23  9:48     ` Carsten Dominik
2007-10-23 10:06       ` Juanma Barranquero
2007-10-23 10:08       ` David Kastrup
2007-10-23 10:36         ` Carsten Dominik
2007-10-23 11:11           ` Juanma Barranquero
2007-10-23 11:39             ` Carsten Dominik
2007-10-23 11:44               ` Juanma Barranquero
2007-10-23 11:54                 ` Carsten Dominik
2007-10-23 12:06                   ` Juanma Barranquero
2007-10-23 20:19                     ` Carsten Dominik
2007-10-23 21:58                       ` Stefan Monnier
2007-10-23 11:16           ` David Kastrup
2007-10-23 11:34             ` Carsten Dominik
2007-10-23 11:49               ` Juanma Barranquero
2007-10-24  2:50                 ` Richard Stallman [this message]
2007-10-23 11:59               ` David Kastrup
2007-10-23 12:06                 ` Carsten Dominik
2007-10-24  2:50                 ` Richard Stallman
2007-10-23 14:43               ` Stefan Monnier
2007-10-23 20:09                 ` Carsten Dominik
2007-10-24  2:50             ` Richard Stallman
2007-10-24  3:33               ` Carsten Dominik
2007-10-29  7:30                 ` Glenn Morris
2007-10-29 22:21                   ` John Wiegley
2007-10-30  6:34                   ` Carsten Dominik
2007-10-23 10:30       ` Miles Bader
2007-10-23  2:11   ` Miles Bader

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=E1IkWJy-0001GS-Fs@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@newartisans.com \
    --cc=lekktu@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=rgm@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).