From: Neil Jerram <neil@ossau.homelinux.net>
To: Rasmus <rasmus@gmx.us>, emacs-orgmode@gnu.org
Subject: Re: Upstream synchronization documentation
Date: Mon, 3 Jul 2017 12:01:32 +0100 [thread overview]
Message-ID: <aca55127-d71a-4c49-ffc9-5c390ae08d04@ossau.homelinux.net> (raw)
In-Reply-To: <87fuedyfij.fsf@gmx.us>
Hi Rasmus,
On 03/07/17 11:35, Rasmus wrote:
> Hi,
>
> The documentation in README_maintainer is a bit outdated
> wrt. synchronizing with upstream Emacs.
>
> I have updated the to best of my knowledge in the attached patch. I would
> be happy to push it, if there are no objections.
>
> It would also be great if someone would let me know about the mistakes
> that are undoubtedly in the draft.
>
> Rasmus
>
I just noticed that your text talks about 'backporting', and wondered if
that is the clearest term to use. To me, a 'backport' usually means
porting a change or fix from the master or development branch to some
older or more stable branch. Whereas in your text I think it is the
other way round, isn't it? (I.e. the Emacs branch is more stable, and
you are talking about porting a fix that someone has made in that branch
to the Org master.) So perhaps 'forward port' would be clearer?
Regards - Neil
next prev parent reply other threads:[~2017-07-03 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 10:35 Upstream synchronization documentation Rasmus
2017-07-03 11:01 ` Neil Jerram [this message]
2017-07-03 15:06 ` Kyle Meyer
2017-07-03 17:31 ` Rasmus Pank Roulund
2017-07-04 0:39 ` Neil Jerram
[not found] ` <2c3a774dd5014c46983c98c8a00758e3@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-07-03 12:11 ` Eric S Fraga
2017-07-03 19:36 ` Kyle Meyer
2017-07-04 6:50 ` Rasmus
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=aca55127-d71a-4c49-ffc9-5c390ae08d04@ossau.homelinux.net \
--to=neil@ossau.homelinux.net \
--cc=emacs-orgmode@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/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).