all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Bastien Guerry <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: Syncing orgcard.tex with upstream Emacs (was: bug#64578: orgcard.tex fixes to allow PDF rendering to be used as a triptych.)
Date: Tue, 05 Dec 2023 20:44:05 -0500	[thread overview]
Message-ID: <87ttowt89m.fsf@kyleam.com> (raw)
In-Reply-To: <87bkb4x1t8.fsf@localhost>

Ihor Radchenko writes:

> Kyle Meyer <kyle@kyleam.com> writes:
>
>> Here is the difference between the two cards, as of the last sync:
>>
>>   -\input org-version.tex
>>   +\def\orgversionnumber{9.6.11}
>>   +\def\versionyear{2023}          % latest update
>>   +\input emacsver.tex
>> ...
>>   +\centerline{For more Emacs documentation, and the \TeX{} source for this card, see}
>>   +\centerline{the Emacs distribution, or {\tt https://www.gnu.org/software/emacs}}
>>   +
>
> Aside: It appears to be only partially documented in
> https://orgmode.org/worg/org-maintenance.html#emacs-sync. In particular,
> the last two lines.

I'm happy to clarify or add to those docs.  I didn't write them, but I
did go through them somewhat recently to better align them with the
actual porting/syncing process.

With respect to the emacs-sync branch, that page currently says

  Typically, Org can be synchronized by copying over files from the
  emacs-sync branch of the Org repository to the master branch of Emacs
  repository. The emacs-sync branch has a few extra changes compared
  with the bugfix branch

Would you like me to add more details about why the branch exists?  How
it's managed?  Something else?

> May we just add
>
>>   +\centerline{For more Emacs documentation, and the \TeX{} source for this card, see}
>>   +\centerline{the Emacs distribution, or {\tt https://www.gnu.org/software/emacs}}
>
> to Org repo?

These lines (or rather what became these lines) were added in Emacs's
4af5981dc75 (Add a comment in generated refcards about the source,
2016-11-17).  I decided to port that commit to emacs-sync rather than a
primary Org branch because I felt it only applied to the Org card
distributed as part of the Emacs tree.  From my notes [*]:

  I'm skipping this because it isn't true when the card is from the Org
  mode repo.

However, if you prefer to include those lines in Org's copy, that's fine
by me.


[*] https://git.kyleam.com/orgmode-backport-notes/tree/orgmode-backports.org?id=35eaf5a21dc776c9f7a880d0a4bf9ffc48213985#n3464


  reply	other threads:[~2023-12-06  1:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12  4:25 bug#64578: orgcard.tex fixes to allow PDF rendering to be used as a triptych José Miguel García Urrutia
2023-07-13 10:51 ` Ihor Radchenko
2023-07-13 14:17   ` José Miguel García Urrutia
2023-09-15  8:50   ` Ihor Radchenko
2023-11-15  9:26     ` Ihor Radchenko
2023-11-19 20:10       ` Bastien Guerry
2023-11-19 20:20         ` José Miguel García Urrutia
2023-12-04 12:51           ` Ihor Radchenko
2023-12-04 17:58             ` José Miguel García Urrutia
2023-12-04 18:17               ` José Miguel García Urrutia
2023-12-05  4:00                 ` Kyle Meyer
2023-12-05 12:37                   ` Syncing orgcard.tex with upstream Emacs (was: bug#64578: orgcard.tex fixes to allow PDF rendering to be used as a triptych.) Ihor Radchenko
2023-12-06  1:44                     ` Kyle Meyer [this message]
2023-12-06 14:13                       ` Ihor Radchenko
2023-12-07  4:53                         ` Kyle Meyer
2023-12-07 10:42                           ` Ihor Radchenko
2023-12-08  3:14                             ` Kyle Meyer
2023-12-05 12:34               ` bug#64578: orgcard.tex fixes to allow PDF rendering to be used as a triptych Ihor Radchenko
2024-01-17 11:47                 ` Ihor Radchenko

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=87ttowt89m.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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.