emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Amin Bandali <bandali@gnu.org>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-element.el change in emacs.git
Date: Sun, 03 Oct 2021 10:46:37 -0400	[thread overview]
Message-ID: <874k9ymaia.fsf@gnu.org> (raw)
In-Reply-To: <87v92hphl1.fsf@alphapapa.net>

Hi Adam, all,

Adam Porter writes:

> 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.

Speaking from personal experience/observations, as far as I know the
Emacs developers don't have strict rules about having uni-directional
changes.  And this is not unique to Org; I've seen similar changes in
both directions in other projects developed outside emacs.git that are
periodically merged into emacs.git.  Eliminating the need for keeping
track of such changes is one potential argument for developing Org --
and those other similar packages -- inside emacs.git itself. :)


  reply	other threads:[~2021-10-03 14:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01  1:31 org-element.el change in emacs.git Adam Porter
2021-10-01  2:31 ` Kyle Meyer
2021-10-01  3:08   ` Adam Porter
2021-10-03 14:46     ` Amin Bandali [this message]
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:

  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=874k9ymaia.fsf@gnu.org \
    --to=bandali@gnu.org \
    --cc=adam@alphapapa.net \
    --cc=emacs-orgmode@gnu.org \


* 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


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).