From: Rasmus <rasmus@gmx.us>
To: emacs-devel@gnu.org
Subject: Re: org-merger questions
Date: Fri, 23 Jun 2017 11:04:26 +0200 [thread overview]
Message-ID: <878tkjoz1h.fsf@gmx.us> (raw)
In-Reply-To: 87k2437v0g.fsf@kyleam.com
Hi Kyle,
Thanks again. I synced your suggested changes.
Kyle Meyer <kyle@kyleam.com> writes:
> It seems that etc/ORG-NEWS, od-manifest-schema-v1.2-os.rnc, and
> od-schema-v1.2-os.rnc all required whitespace cleanups. These cleanups
> are now included in Org's maint (and cherry-picked to the emacs-sync branch).
Indeed. Those were the ones it complained about.
>> A few problems in scratch/org-mode-merge:
>
> [...]
>
>> * I made the mistake of not looking at ORG-NEWS for backports, so
>> scratch/org-mode-merge is reverting a few Emacs commits here. I'll
>> backport these
>
> I've backported all the changes to ORG-NEWS in maint (and cherry-picked
> them to the emacs-sync branch).
>
> Please consider using Org files from the emacs-sync branch instead of
> the release_9.0.9 tag. The emacs-sync branch is a superset of the last
> release, but it contains a few more changes that are specific for Emacs.
Cool. Thanks a lot. As said in the previous post, I didn’t use this
branch.
> You can see these changes in the Org repo with
>
> git diff release_9.0.9..origin/emacs-sync
>
> (This diff also includes the whitespace cleanup and ORG-NEWS backports
> that were cherry-picked to emacs-sync because they are in the maint
> branch after release_9.0.9 but should be in the 9.0.9 sync.)
I updated the files in question to the "emacs-sync" version.
I had to change the version in orgcard.tex as it wasn’t 9.0.9.
>> [...] and I can also add your ORG-NEWS formatting changes to the Org repo.
>
> I don't understand the formatting changes made in 5cfdf8dd17 (; Fix
> ORG-NEWS formatting in previous commit, 2017-06-22). Aside from fixing
> the alignment of a table that already seems correct in Org's ORG-NEWS,
> all the changes seem to be space to tab conversions. Are these
> necessary?
I must have done a mistake. ORG-NEWS seems to always change when I open
with my normal Emacs configuration. So I redid the whitespace cleanup
with "emacs -q" but apparently that also induced unnecessary changes.
Thanks for fixing this!
Rasmus
--
Enough with the blah blah!
next prev parent reply other threads:[~2017-06-23 9:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 15:09 org-merger questions Rasmus
2017-06-21 15:23 ` Kaushal Modi
2017-06-21 16:16 ` Bastien Guerry
2017-06-22 10:31 ` Rasmus
2017-06-22 10:46 ` Yuri Khan
2017-06-22 16:01 ` Kyle Meyer
2017-06-22 18:11 ` Kyle Meyer
2017-06-23 9:04 ` Rasmus [this message]
2017-06-23 14:19 ` Kyle Meyer
2017-06-23 8:47 ` Rasmus
2017-06-23 14:30 ` Kyle Meyer
2017-06-23 14:37 ` Rasmus
2017-06-25 16:10 ` Kaushal Modi
2017-06-29 8:54 ` Rasmus
2017-06-29 9:12 ` Bastien Guerry
2017-06-29 16:13 ` John Wiegley
2017-07-03 7:19 ` Bastien
2017-07-03 15:56 ` Emacs master now updated to Org 9.0.9 (Was: org-merger questions) Kaushal Modi
2017-07-04 7:54 ` Emacs master now updated to Org 9.0.9 Bastien Guerry
2017-07-13 0:36 ` numbchild
2017-10-02 9:25 ` org-merger questions Bastien Guerry
2017-10-02 9:41 ` Rasmus
2017-10-02 9:46 ` Rasmus
2017-10-02 16:05 ` Eli Zaretskii
2017-10-11 22:31 ` Org mode update missing in NEWS (Was: Re: org-merger questions) Kaushal Modi
2017-10-12 7:54 ` Eli Zaretskii
2017-10-15 10:37 ` Org mode update missing in NEWS Rasmus
2017-06-21 15:27 ` org-merger questions Kyle Meyer
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=878tkjoz1h.fsf@gmx.us \
--to=rasmus@gmx.us \
--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 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).