emacs-orgmode@gnu.org archives
 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: Thu, 07 Dec 2023 22:14:43 -0500	[thread overview]
Message-ID: <871qbxfkrg.fsf@kyleam.com> (raw)
In-Reply-To: <875y1a47ku.fsf@localhost>

Ihor Radchenko writes:

> I see now. I guess I did not really have a full understanding of the
> purpose of emacs-sync. So, it might be helpful to add a similar
> explanation to worg/org-maintenance.org.

Okay, I'll plan to do that.

>> I don't see what problem it solves.  It's moving the divergence to a
>> different file (that would still be tracked in emacs-sync), and it adds
>> one more Org-specific wrinkle to the Emacs tree.  (Also, the orgcard
>> source would still be different given the upstream hunk in the diff I
>> posted in my last message.)
>
> My idea was not to sync that another extra file at all and leave it in
> Emacs repo only.

I see.  Not that it matters given what you say below, but I would
probably lean toward keeping track of such a file in emacs-sync.

> But the same will not work for xml and other diverging
> files. I now don't see any reason to change the existing state of affairs.

All right, thanks for your input.  I'll try to improve
worg/org-maintenance.org as discussed.


      reply	other threads:[~2023-12-08  3:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGQFwfgr-=jqC_SKLnsHxXgABhoZRTGL_ZYwuu0EgJ7YAG0wPw@mail.gmail.com>
     [not found] ` <874jm8ythh.fsf@localhost>
     [not found]   ` <875y4bbz13.fsf@localhost>
     [not found]     ` <87r0kr9xke.fsf@localhost>
     [not found]       ` <871qcl33o2.fsf@gnu.org>
     [not found]         ` <CAGQFwfhFV97eAwWYN_P6EoVEHeS+sH2oOM0_0Qwac8zzspSnjg@mail.gmail.com>
     [not found]           ` <87ttoym8qu.fsf@localhost>
     [not found]             ` <CAGQFwfii4m8_i9Y-4GdUNMggzmYuc2uMu9aT7Zmg8x5oUi6-uQ@mail.gmail.com>
     [not found]               ` <CAGQFwfifY_rNYLBwNz0prQVE2YHiekciAVp6JHTtHi0ZwoGKEw@mail.gmail.com>
     [not found]                 ` <87wmttti1k.fsf@kyleam.com>
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
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 [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=871qbxfkrg.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 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).