From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Carsten Dominik" <carsten.dominik@gmail.com>
Cc: John Wiegley <johnw@newartisans.com>,
emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
Glenn Morris <rgm@gnu.org>
Subject: Re: recent changes to org files
Date: Tue, 23 Oct 2007 13:11:33 +0200 [thread overview]
Message-ID: <f7ccd24b0710230411n2587b04cp6ac663ed502b546b@mail.gmail.com> (raw)
In-Reply-To: <1100BA17-7426-4C73-9EF0-FF90C1859B47@gmail.com>
On 10/23/07, Carsten Dominik <carsten.dominik@gmail.com> wrote:
> But replacing, for example `next-line' by `forward-line' in an
> outline-like mode
> is a bug, and such changes should be run by the maintainer who knows the
> code well.
I think it is safe to assume whomever did that change didn't know it
was a bug... :) Surely he though it was a simple fix for a simple
problem.
> Things like this have happened to me in the past, again
> recently.
> 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.
There's a difference between spending your days on emacs-devel, and
spending a bit of time tracking changes to Org in the Emacs CVS. I'm
not saying that you should do it (it's your time, not mine), but if
you don't, then don't be surprised if sometimes problems like this one
happen, and don't blame just the committer.
> If I would follow Stefan' advice and only check in diffs, the `next-
> line' code would
> be broken now.
Surely you're not saying that Stefan spoke *against* fixing bugs in
the CVS, are you?
Juanma
next prev parent reply other threads:[~2007-10-23 11:11 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7ccd24b0710230411n2587b04cp6ac663ed502b546b@mail.gmail.com \
--to=lekktu@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.