unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Radon Rosborough <radon.neon@gmail.com>
To: Phillip Lord <phillip.lord@russet.org.uk>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Using Org as the source format to generate org.texi
Date: Mon, 12 Mar 2018 14:04:29 -0700	[thread overview]
Message-ID: <CADB4rJEOT6Twy8yCOP1+=ejepEdKMAJm0pbUVQB8YYvWqdUQ5w@mail.gmail.com> (raw)
In-Reply-To: <87vae3zobm.fsf@russet.org.uk>

> As it happens I have a version of this now. It would lead to the
> slightly strange situation that the build would refer to org-mode
> functions which are not actually hosted in the repo. So, it would mean
> that you could not build Emacs from a clean clone of the Emacs repo
> without access to the ELPA repo (i.e. a local clone).

I don't understand why this is the case. Currently, a version of Org
is bundled in Emacs core. Where does ELPA enter into it? Are you
talking about a hypothetical future situation where Org is not bundled
with Emacs? If so, then why would the Org manual even exist in Emacs
core?

Thanks,
Radon



  parent reply	other threads:[~2018-03-12 21:04 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06 18:04 Using Org as the source format to generate org.texi Bastien
2018-03-06 20:20 ` Stefan Monnier
2018-03-06 20:24   ` Kaushal Modi
2018-03-06 21:54   ` Achim Gratz
2018-03-07  0:22   ` Bastien
2018-03-07 17:43     ` Eli Zaretskii
2018-03-07 17:52       ` Kaushal Modi
2018-03-08 10:04         ` Bastien Guerry
2018-03-08  7:28       ` Michael Albinus
2018-03-08 10:06         ` Bastien Guerry
2018-03-08 10:13       ` Bastien Guerry
2018-03-07 17:39   ` Glenn Morris
2018-03-07 22:57   ` Richard Stallman
2018-03-09 11:30     ` Bastien
2018-03-10 21:26     ` Nicolas Goaziou
2018-03-11  3:40       ` Eli Zaretskii
2018-03-11 14:59       ` Michael Albinus
2018-03-11 18:13         ` Nicolas Goaziou
2018-03-11 23:26       ` Richard Stallman
2018-03-12 14:07         ` Nicolas Goaziou
2018-03-12 15:51           ` Eli Zaretskii
2018-03-12 16:42             ` Nicolas Goaziou
2018-03-12 17:32               ` Eli Zaretskii
2018-03-12 17:57                 ` Nicolas Goaziou
2018-03-12 20:16                   ` Eli Zaretskii
2018-03-12 21:37                     ` Nicolas Goaziou
2018-03-13 15:55                       ` Eli Zaretskii
2018-03-13 17:24                         ` Nicolas Goaziou
2018-03-13 17:43                           ` Eli Zaretskii
2018-03-13 21:37                             ` Nicolas Goaziou
2018-04-14 17:10                         ` @key{...} mis-use (was: Using Org as the source format to generate org.texi) Nicolas Goaziou
2018-04-19  9:22                           ` Eli Zaretskii
2018-03-06 21:30 ` Using Org as the source format to generate org.texi Paul Eggert
2018-03-07  0:19   ` Bastien
2018-03-07  1:08     ` Paul Eggert
2018-03-07  7:33       ` Achim Gratz
2018-03-09 17:52         ` Achim Gratz
2018-03-09 18:02           ` Paul Eggert
2018-03-09 18:23             ` Achim Gratz
2018-03-07 17:41       ` Glenn Morris
2018-03-09 11:19         ` Phillip Lord
2018-03-12 17:12           ` Glenn Morris
2018-03-09 17:39         ` Achim Gratz
2018-03-10 20:07           ` Phillip Lord
2018-03-11  3:00             ` Paul Eggert
2018-03-11  3:55               ` Stefan Monnier
2018-03-11 21:46                 ` Phillip Lord
2018-03-12 21:04             ` Radon Rosborough [this message]
2018-03-13  9:10               ` Phillip Lord
2018-03-13 12:29                 ` Stefan Monnier
2018-03-13 16:47                   ` Phillip Lord
2018-04-14 19:15 ` Joshua Branson

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADB4rJEOT6Twy8yCOP1+=ejepEdKMAJm0pbUVQB8YYvWqdUQ5w@mail.gmail.com' \
    --to=radon.neon@gmail.com \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-devel@gnu.org \
    --cc=phillip.lord@russet.org.uk \
    /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.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).