From: Glenn Morris <rgm@gnu.org>
To: Bastien <bzg@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Org merging [was Re: next pretest]
Date: Wed, 13 Aug 2014 14:27:51 -0400 [thread overview]
Message-ID: <ra978dz2w.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 8761hwsxt4.fsf@bzg.ath.cx
Bastien wrote:
> Well, it's a matter of timing.
Org already gets special treatment. I don't see what else can be done.
> Fixing bugs in the stable Org branch seems preferrable than merging
> Org with Emacs, because I suspect the stable Org branch has more
> testers than emacs-24.
I suggest that after this release we stop keeping Org in the Emacs
*repository*. Motivation:
1) It's usually months out-of-date.
2) Merging has been a frequent problem, wastes resources, is not a
priority for you, and no-one else seems interested in doing it.
3) As you say, probably it has relatively few users anyway. Anyone
capable of getting Emacs from VCS can get Org from elpa or wherever;
I suspect most who want to use it do.
4) Almost no-one changes Org in the Emacs repo.
5) Org bugs reported to bug-gnu-emacs get little attention. I don't
think I ever see any of the other Org people apart from you comment on
bug-gnu-emacs reports. The reports usually refer to versions of Org not
even in Emacs.
6) I know you have frequent problems with people wanting to use a
different Org version than the one in Emacs.
7) It doesn't get any benefit from Emacs pretests, owing to point 1.
We can still include it future release *tarballs*, if you like, using a
mechanism to be determined before the next release. But keeping it in
the *repository* seems pointless.
next prev parent reply other threads:[~2014-08-13 18:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 15:43 next pretest Glenn Morris
2014-08-11 15:51 ` Eli Zaretskii
2014-08-12 8:49 ` Bastien
2014-08-12 14:42 ` Eli Zaretskii
2014-08-13 6:34 ` Bastien
2014-08-12 15:57 ` Glenn Morris
2014-08-13 6:33 ` Bastien
2014-08-13 18:27 ` Glenn Morris [this message]
2014-08-13 19:46 ` Org merging [was Re: next pretest] Stefan Monnier
2014-08-13 20:39 ` Achim Gratz
2014-08-13 21:23 ` Stefan Monnier
2014-08-14 6:43 ` Achim Gratz
2014-08-14 13:06 ` Stefan Monnier
2014-08-14 18:53 ` Achim Gratz
2014-08-14 19:20 ` Stefan Monnier
2014-08-14 19:31 ` Achim Gratz
2014-08-14 22:46 ` Stefan Monnier
2014-08-14 5:34 ` Bastien
2014-08-14 7:08 ` Achim Gratz
2014-08-14 12:56 ` Stefan Monnier
2014-08-14 13:21 ` Eric Abrahamsen
2014-08-14 15:00 ` Stefan Monnier
2014-08-14 15:40 ` Eric Abrahamsen
2014-08-14 19:12 ` Achim Gratz
2014-08-15 2:52 ` Stefan Monnier
2014-08-15 15:57 ` Achim Gratz
2014-08-15 18:45 ` Stefan Monnier
2014-08-14 12:50 ` Stefan Monnier
2014-08-14 5:27 ` Bastien
2014-08-12 8:46 ` next pretest Bastien
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=ra978dz2w.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=bzg@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 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.