From: Carsten Dominik <carsten.dominik@gmail.com>
To: David Kastrup <dak@gnu.org>
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 14:06:29 +0200 [thread overview]
Message-ID: <06651AC0-9C5D-4BB6-8B33-352B9C8B5A16@gmail.com> (raw)
In-Reply-To: <863aw26nye.fsf@lola.quinscape.zz>
On Oct 23, 2007, at 1:59 PM, David Kastrup wrote:
> Your words don't match your proposed way of working. Emacs
> maintainance quite often means bulk changes: new interfaces and
> semantics are introduced, and things like the multitty changes and the
> unicode changes necessitate global work (as do added bytecompiler
> warnings). It is not feasible to do the update work only after
> figuring out prospective maintainers for every file. The only hope to
> get things like this done is to do the changes and let the maintainers
> check for them. And merge time is certainly an important point of
> time for checking it (though regularly checking for diffs in that area
> is not amiss either for a maintainer actually interested in his code).
>
> If your workflow does not permit fixes to be applied to Emacs CVS, the
> only sane solution short of adjusting your workflow is to remove
> org-mode from Emacs CVS. Only in that manner can it be assured that
> bug fixes and interface changes and other things can actually persist.
Well, don't turn my words in my mouth. I believe so far I have been
constructive in
this discussion and so have you. Let's keep it that way.
-- Carsten
next prev parent reply other threads:[~2007-10-23 12:06 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
2007-10-23 11:59 ` David Kastrup
2007-10-23 12:06 ` Carsten Dominik [this message]
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=06651AC0-9C5D-4BB6-8B33-352B9C8B5A16@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=dak@gnu.org \
--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).