all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@gnu.org>
To: Bastien <bzg@altern.org>
Cc: "Jambunathan K." <kjambunathan@gmail.com>,
	schulte eric <schulte.eric@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Merging Org 7.8.02 before Emacs 24.1
Date: Thu, 29 Dec 2011 12:42:10 +0800	[thread overview]
Message-ID: <87boqshtul.fsf@gnu.org> (raw)
In-Reply-To: <87vcp3hfuh.fsf@gnu.org> (Bastien's message of "Mon, 26 Dec 2011 09:55:34 +0100")

Bastien <bzg@altern.org> writes:

> IMHO the feature freeze would make more sense if there was a deadline
> for the Emacs release.  Is there one?

There is no deadline.  It will take at least a few more months, but we
are close enough that a further Org merge after this one will most
likely be unacceptable, unless it is purely bug fixes.

If you guys are continuing to add features upstream, I recommend setting
up a bugfix-only branch or some other setup for channeling upstream bug
fixes into the Emacs trunk, for the duration of the Emacs pretest.



  parent reply	other threads:[~2011-12-29  4:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23 13:54 Merging Org 7.8.02 before Emacs 24.1 Bastien
2011-12-24  4:24 ` Jambunathan K
2011-12-24  7:31   ` Jambunathan K
2011-12-24  8:09     ` Bastien
2011-12-24  5:11 ` Leo
2011-12-26  7:44 ` Chong Yidong
2011-12-26  8:55   ` Bastien
2011-12-27  7:19     ` Jambunathan K
2011-12-27 10:47       ` Lennart Borgman
2011-12-29  4:42     ` Chong Yidong [this message]
2011-12-31  8:27       ` Bastien
2011-12-31 10:39         ` Stefan Monnier
2011-12-31 11:41           ` Bastien
2011-12-31 17:17             ` Eric Schulte
2011-12-26 21:32   ` Eric Schulte
2011-12-29  4:36 ` Chong Yidong
2011-12-29 16:41   ` Bastien
2012-01-03 19:45   ` 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=87boqshtul.fsf@gnu.org \
    --to=cyd@gnu.org \
    --cc=bzg@altern.org \
    --cc=emacs-devel@gnu.org \
    --cc=kjambunathan@gmail.com \
    --cc=schulte.eric@gmail.com \
    /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.