From: Eli Zaretskii <eliz@gnu.org>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-devel@gnu.org
Subject: Re: OK to push Org bugfixes for next Emacs?
Date: Tue, 08 May 2018 05:26:18 +0300 [thread overview]
Message-ID: <83vabyq3w5.fsf@gnu.org> (raw)
In-Reply-To: <87y3gv6sf4.fsf@gmx.us> (message from Rasmus on Mon, 07 May 2018 23:56:47 +0200)
> From: Rasmus <rasmus@gmx.us>
> Date: Mon, 07 May 2018 23:56:47 +0200
>
> Can the Org bugfixes for v9.1 be part of a subsequent minor release?
Yes, of course.
prev parent reply other threads:[~2018-05-08 2:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 18:24 OK to push Org bugfixes for next Emacs? Rasmus
2018-05-05 18:39 ` Eli Zaretskii
2018-05-07 21:56 ` Rasmus
2018-05-08 2:26 ` Eli Zaretskii [this message]
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=83vabyq3w5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rasmus@gmx.us \
/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).