emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Detlev Zundel <dzu@akk.org>
Cc: 18401@debbugs.gnu.org
Subject: bug#18401: 24.4.50; emerge-files fails for org files
Date: Thu, 11 Sep 2014 12:44:17 -0400	[thread overview]
Message-ID: <icoaum3y5a.fsf__33823.5876792625$1410453989$gmane$org@fencepost.gnu.org> (raw)
In-Reply-To: <m2oaumv8w9.fsf@deepthought.outer.space.org> (Detlev Zundel's message of "Thu, 11 Sep 2014 10:49:58 +0200")

Detlev Zundel wrote:

> problem and lingers for a while now.  Who can merge the org repository?
> Is there something that an outsider like me can do to help?

Thanks for asking! :)

Anyone with a copy of the Org repo and the Emacs repo can generate the
diff that needs to be applied from the former to the latter.

Anyone with write access to the Org repo can get write access to the
Emacs repo and apply that diff. (This is a generalization, but I think
it is true. E.g. I assume all people with Org write access have FSF
assignments.)

However, I think this is wasted effort, so I have suggested not doing it
any more; http://lists.gnu.org/archive/html/emacs-devel/2014-08/msg00298.html .

  parent reply	other threads:[~2014-09-11 16:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2d2bc1kye.fsf@deepthought.outer.space.org>
2014-09-03 21:12 ` bug#18401: 24.4.50; emerge-files fails for org files Glenn Morris
2014-10-12 12:12   ` Bastien
     [not found] ` <ama96ge7c4.fsf@fencepost.gnu.org>
2014-09-11  8:49   ` Detlev Zundel
     [not found]   ` <m2oaumv8w9.fsf@deepthought.outer.space.org>
2014-09-11 16:44     ` Glenn Morris [this message]
     [not found]     ` <icoaum3y5a.fsf@fencepost.gnu.org>
2014-09-12  9:37       ` Detlev Zundel
2014-09-15 14:21 ` Bastien
2014-09-15 18:27   ` Detlev Zundel

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='icoaum3y5a.fsf__33823.5876792625$1410453989$gmane$org@fencepost.gnu.org' \
    --to=rgm@gnu.org \
    --cc=18401@debbugs.gnu.org \
    --cc=dzu@akk.org \
    /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).