From: Adam Porter <firstname.lastname@example.org> To: email@example.com Subject: Re: org-element.el change in emacs.git Date: Thu, 30 Sep 2021 22:08:42 -0500 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Hi Kyle, Kyle Meyer <firstname.lastname@example.org> writes: > Thanks for the heads up. > > I monitor Org-related changes to the Emacs repo and port them to Org's. > Entering into Emacs release periods, I tend to look at least once a day > so that porting doesn't hold up cutting a bugfix release and syncing. > Other times, it's not as frequent, but usually not less than once a > week. Well, I guess I need to follow the mailing list more closely; if I did, I'd probably have already known that. :) > None of that is to say that flagging an important commit isn't > appreciated. Just setting expectations about what the normal intake > looks like. I don't know, for what we're paying you, I think something like a 1-hour turnaround time would be more appropriate... ;) > (Fwiw a log of the considered commits is available at > <https://git.kyleam.com/orgmode-backport-notes/plain/orgmode-backports.org>.) I didn't know about that URL. That's 8 years of faithful, thankless maintenance. Thanks for your work on Org. :) By the way, I'm curious, not having always followed the internal details of Org's development over the years: why are changes like that made to emacs.git and merged back into Org, instead of being made in Org and then merged back into Emacs with the next sync? It seems like it could be a burden, requiring someone like you to track them and merge them, but there's probably a good reason for this workflow.
next prev parent reply other threads:[~2021-10-01 3:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-01 1:31 Adam Porter 2021-10-01 2:31 ` Kyle Meyer 2021-10-01 3:08 ` Adam Porter [this message] 2021-10-03 14:46 ` Amin Bandali 2021-10-04 10:31 ` Adam Porter
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: org-element.el change in emacs.git' \ /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
Code repositories for project(s) associated with this 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).