From: Alan Mackenzie <acm@muc.de>
To: Nic Ferrier <nferrier@ferrier.me.uk>
Cc: David Kastrup <dak@gnu.org>, emacs-devel@gnu.org
Subject: Re: ELPAing all the GNU manuals
Date: Sun, 28 Sep 2014 12:48:47 +0000 [thread overview]
Message-ID: <20140928124847.GD3157@acm.acm> (raw)
In-Reply-To: <87oau0t2yy.fsf@ferrier.me.uk>
Hello again, Nic.
On Sun, Sep 28, 2014 at 12:10:45PM +0100, Nic Ferrier wrote:
> David Kastrup <dak@gnu.org> writes:
> > Alan Mackenzie <acm@muc.de> writes:
> >> You'll get one more non-authoritative place to obtain all these
> >> manuals, and from this place they're not going to be up to date,
> >> unless you figure out some mechanism of keeping them up to date.
> >> Keeping them up to date is going to be a lot of work.
> > Uh, I don't _want_ my info manuals to be up to date. I want them to
> > correspond to the software version I have installed. I have nothing to
> > gain from using copy&paste of some code from a manual that is not yet
> > supported by my software.
> I've just realized I am asking for permission and I should just be
> doing.
Another reason for not doing it is it might be bloating ELPA with what
it's not really for. This is what has happened at my day job, where our
source code repository has become the default place to store anything
and everything, like test results and reports on visits to suppliers.
The said repositiory has swollen to several 10s of Gigabytes.
But I don't know ELPA well enough to judge whether random manuals are
appropriate there. Doesn't "ELPA" stand for "elisp <something or
other>"?
> But here's one reason why things do go into ELPA. General negativity
> being almost always the first reaction on this list.
:-) Well, you did explicitly ask for opinions. You got some.
> Nic
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2014-09-28 12:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 9:36 ELPAing all the GNU manuals Nic Ferrier
2014-09-28 10:47 ` Alan Mackenzie
2014-09-28 11:06 ` David Kastrup
2014-09-28 11:10 ` Nic Ferrier
2014-09-28 12:12 ` joakim
2014-09-28 12:41 ` David Kastrup
2014-09-28 12:48 ` Alan Mackenzie [this message]
2014-09-28 12:49 ` Eric Brown
2014-09-28 16:37 ` Stefan Monnier
2014-09-28 18:17 ` Nic Ferrier
2014-09-28 20:58 ` Glenn Morris
2014-09-29 10:32 ` Thomas Koch
2014-09-29 16:51 ` Nic Ferrier
2014-09-29 20:49 ` Richard Stallman
2014-09-29 12:34 ` Matthias Meulien
2014-09-29 13:25 ` Eli Zaretskii
2014-09-29 19:35 ` Matthias Meulien
2014-09-29 20:00 ` Eli Zaretskii
2014-09-29 20:47 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140928124847.GD3157@acm.acm \
--to=acm@muc.de \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nferrier@ferrier.me.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.