unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: ELPAing all the GNU manuals
Date: Sun, 28 Sep 2014 14:41:55 +0200	[thread overview]
Message-ID: <87h9zrlxws.fsf@fencepost.gnu.org> (raw)
In-Reply-To: m338bcosee.fsf@exodia.verona.se

joakim@verona.se writes:

> Nic Ferrier <nferrier@ferrier.me.uk> writes:
>
>> 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.
>>
>>
>> But here's one reason why things do go into ELPA. General negativity
>> being almost always the first reaction on this list.
>
> So, I will play good cop.
>
> To me it sounds like a cool idea.
>
> Apart from just being good cop, I see some actual benefits.
>
> There is precedence in the Java world for this sort of thing, and there
> its pretty useful.
>
> In the Emacs world, we would gain increased visibility of the GNU
> world from within Emacs. ELPA browser frontends will also be nicer.
>
> Now over to the bad cops...

Uh, you just smoked all the confiscated weed.  Now what?

-- 
David Kastrup




  reply	other threads:[~2014-09-28 12:41 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 [this message]
2014-09-28 12:48       ` Alan Mackenzie
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

  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=87h9zrlxws.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.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.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).