From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Vicente Vera <vicentemvp@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Make org-fill-paragraph behave as Emacs 26.1 fill-paragraph
Date: Sun, 17 Jun 2018 21:40:20 +0200 [thread overview]
Message-ID: <87fu1li4m3.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAMfbzvDmF8CWq_v2miq7E43k_DbSkX_q_XzQ0o4R4rJ_r8_fqQ@mail.gmail.com> (Vicente Vera's message of "Sun, 17 Jun 2018 12:19:28 -0400")
Hello,
Vicente Vera <vicentemvp@gmail.com> writes:
> The 'next' branch will be merged with 'master' for Org 9.2 release?
No. "next" will be merged with master after Org 9.2 release. So it's
really for Org 9.3.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2018-06-17 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 16:15 Make org-fill-paragraph behave as Emacs 26.1 fill-paragraph Vicente Vera
2018-06-14 20:07 ` Nicolas Goaziou
2018-06-17 16:19 ` Vicente Vera
2018-06-17 19:40 ` Nicolas Goaziou [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fu1li4m3.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=vicentemvp@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).