From: David Kastrup <dak@gnu.org>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: John Wiegley <johnw@newartisans.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Glenn Morris <rgm@gnu.org>,
emacs-devel@gnu.org
Subject: Re: recent changes to org files
Date: Tue, 23 Oct 2007 13:16:09 +0200 [thread overview]
Message-ID: <86bqaq6pza.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <1100BA17-7426-4C73-9EF0-FF90C1859B47@gmail.com> (Carsten Dominik's message of "Tue\, 23 Oct 2007 12\:36\:04 +0200")
Carsten Dominik <carsten.dominik@gmail.com> writes:
> I don't have the time to spend my days on emacs-devel, my energy
> goes into making org-mode as good as I can. The version of org-mode
> that is tested the most is the one I distribute, and the most likely
> to not have any bugs.
That assumes that more people use the org-mode from your web site than
the org mode in Emacs, since using org-mode is a sort of testing.
If that is the case, there is little point in distributing org-mode as
part of Emacs.
But I really doubt it.
> That is the one I am checking into. Emacs. When I see changes made
> to org-mode in Emacs I am incorporating them into my master copy if
> they make sense, and only then.
>
> If I would follow Stefan' advice and only check in diffs, the `next-
> line' code would be broken now.
If indeed this would be the case (and I don't see that right now), it
would be broken in a documented and isolatable way, and for a reason.
This reason remains to exist. Overwriting the change without comment
or documentation means that the same reason will possibly result in
the same change being made later on.
If some code is in violation of the Emacs development guidelines, the
reason should be documented so that people _know_ about it and leave
it alone. Silently reverting the change in a manner that looks like
an accident will not achieve this.
> I do agree, I am not battling, I am doing as good as I can and I I
> sometimes slip. But if I am the maintainer of org-mode in Emacs,
> than I and no one else decides what goes into the mode and what not.
> If people disagree, and I will quit maintaining this mode inside
> Emacs.
Basically you are asking that nothing, including bug fixes, may be
committed to org-mode except by yourself. Then there is no point in
having org-mode inside of Emacs' CVS.
Being a maintainer does not mean that nobody else may do work on the
code. It means that people in general respect you having the last
word. But it is the last, not the only word.
--
David Kastrup
next prev parent reply other threads:[~2007-10-23 11:16 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 [this message]
2007-10-23 11:34 ` Carsten Dominik
2007-10-23 11:49 ` Juanma Barranquero
2007-10-24 2:50 ` Richard Stallman
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=86bqaq6pza.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=carsten.dominik@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=johnw@newartisans.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).