emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Missing changes
Date: Wed, 06 Sep 2023 23:22:47 -0400	[thread overview]
Message-ID: <878r9izmyg.fsf@kyleam.com> (raw)
In-Reply-To: <874jk6hhmk.fsf@yahoo.com>

Po Lu writes:

> These changes made to lisp/org within the Emacs repository are absent
> from orgmode.git:
>
> * | 73b24a41412..: Po Lu 2023-08-23 Make org-mouse compatible with touch screen event emulation
> * | 4f714dc0813..: Po Lu 2023-08-20 Support desktop notifications on Android
> * | 5856ea5e4e8..: Po Lu 2023-08-17 Introduce support for Desktop Notifications on Haiku
>
> Would anyone care to see to it that they are transferred into the Org
> repository?

Those commits are on Emacs's master branch.  We're up to date with the
emacs-29 branch, but I've yet to port any of the Emacs's master-specific
Org changes to Org's main branch.  I started working on it last weekend,
so it should happen soon-ish.  In any case, all the currently unported
master-specific changes would of course be ported to Org's main before
we start syncing that to Emacs's master.

You can find all of these commits listed at

  https://git.kyleam.com/orgmode-backport-notes/tree/orgmode-backports.org

It's not in your list above, but there's also your 9082b4e6ee2 (Make
binaries distributed with Emacs work on Android, 2023-01-24).  That, by
the way, will need to be adjusted to stay compatible with previous Emacs
versions that don't have a ctags-program-name variable defined.


  reply	other threads:[~2023-09-07  3:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874jk6hhmk.fsf.ref@yahoo.com>
2023-09-07  1:55 ` Missing changes Po Lu
2023-09-07  3:22   ` Kyle Meyer [this message]
2023-09-07  4:11     ` Po Lu
2023-09-07 11:54       ` 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

  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=878r9izmyg.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=luangruo@yahoo.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).