From: Kyle Meyer <kyle@kyleam.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: David Masterson <dsmasterson@outlook.com>, Bastien <bzg@gnu.org>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug: Orgguide missing in Org-9.3 package [9.3 (9.3-elpa @ /home/David/.emacs.d/elpa/org-9.3/)]
Date: Mon, 16 Dec 2019 03:41:48 +0000 [thread overview]
Message-ID: <87k16x7x8j.fsf@kyleam.com> (raw)
In-Reply-To: <87y2vfot7w.fsf@nicolasgoaziou.fr>
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>> Sorry, I don't have write access. But this issue seems to be about the
>> Org ELPA tarball, so I don't understand how it'd be related to the
>> recent Org sync with the Emacs repo.
>
> That's because I misread the bug report and though it was related to
> Emacs master branch.
>
> In any case, Org ELPA tarball and files merged with Emacs are two
> different things. IOW, even if ELPA tarball contains the Org guide, it
> is not sufficient for Emacs to ship it, too. So this also needs to be
> fixed on the Emacs' side, AFAIU.
Agreed, we should include orgguide.texi alongside org.tex in Emacs's
doc/misc/. I've cc'd Bastien in case he'd like to adjust the latest
sync, though, given that orgguide has existed for a long time and has
never been included in the Emacs repo (AFAICS), I also don't see a
problem with waiting for the next sync until handling it.
>> Assuming there's not a good reason that orgguide is omitted, I think
>> fixing this is just a matter of adding orgguide to server.mk's
>> ORGELPA variable.
>
> I have no objection, but, per above, we should check if there's
> something to do in the Emacs repository, too.
OK, I'll apply that patch.
Thanks.
prev parent reply other threads:[~2019-12-16 3:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 5:26 Bug: Orgguide missing in Org-9.3 package [9.3 (9.3-elpa @ /home/David/.emacs.d/elpa/org-9.3/)] David Masterson
2019-12-12 8:57 ` Nicolas Goaziou
2019-12-13 3:23 ` Kyle Meyer
2019-12-14 14:52 ` Nicolas Goaziou
2019-12-16 3:41 ` Kyle Meyer [this message]
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=87k16x7x8j.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=bzg@gnu.org \
--cc=dsmasterson@outlook.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).