From: Glenn Morris <rgm@gnu.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: elpa.gnu.org packages in an Emacs checkout
Date: Fri, 25 Feb 2011 15:43:47 -0500 [thread overview]
Message-ID: <amei6v3kvw.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 87zkpj986x.fsf@lifelogs.com
Ted Zlatanov wrote:
> OK. Which ones of:
>
> nt/INSTALL
> doc/emacs/maintaining.texi
> doc/emacs/anti.texi
> doc/misc/faq.texi
> admin/notes/bzr
> admin/notes/bugtracker
> admin/bzrmerge.el
> INSTALL
> INSTALL.BZR
> etc/THE-GNU-PROJECT
> etc/CONTRIBUTE
>
> should I do (trying to avoid unnecessary modifications)?
Several of those suggestions make no sense (perhaps I missed the sarcasm).
I would say for sure mention elpa.gnu.org in:
doc/misc/faq.texi
etc/MORE.STUFF
etc/NEWS (already a brief mention I see)
and at some point closer to the release in the Emacs manual.
I wouldn't mention the bzr branch in any of those places, because that
detail is not relevant to users. They should just go through
elpa.gnu.org. Is there any reason users need to know about the bzr
branch at all? It could be mentioned in a note on http://elpa.gnu.org.
As to documenting the existence of the elpa branch for developers, I
don't know what there is to say, but I think admin/notes/elpa is the
right place.
But see what others think since I haven't thought about this much.
prev parent reply other threads:[~2011-02-25 20:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 14:06 debbugs.el Michael Albinus
2011-02-23 17:25 ` debbugs.el Chong Yidong
2011-02-24 8:06 ` debbugs.el Reiner Steib
2011-02-24 11:33 ` debbugs.el Michael Albinus
2011-02-24 23:44 ` debbugs.el Evgeny M. Zubok
2011-02-25 10:55 ` debbugs.el Michael Albinus
2011-02-25 16:51 ` debbugs.el Evgeny M. Zubok
2011-03-01 10:15 ` debbugs.el Michael Albinus
2011-03-02 15:56 ` debbugs.el Evgeny M. Zubok
2011-02-25 3:37 ` debbugs.el Lars Ingebrigtsen
2011-02-25 8:17 ` debbugs.el Eli Zaretskii
2011-02-25 8:33 ` debbugs.el Michael Albinus
2011-02-25 8:54 ` debbugs.el Eli Zaretskii
2011-02-25 9:29 ` debbugs.el Miles Bader
2011-02-25 9:55 ` debbugs.el Eli Zaretskii
2011-02-25 15:43 ` debbugs.el Stefan Monnier
2011-02-25 15:52 ` debbugs.el Eli Zaretskii
2011-02-25 9:59 ` debbugs.el Lars Ingebrigtsen
2011-02-25 10:10 ` debbugs.el Eli Zaretskii
2011-02-24 17:11 ` debbugs.el Karl Fogel
2011-02-24 18:21 ` debbugs.el Chong Yidong
2011-02-24 18:43 ` debbugs.el Karl Fogel
2011-02-25 0:42 ` debbugs.el Stephen J. Turnbull
2011-02-25 14:49 ` debbugs.el Ted Zlatanov
2011-02-25 15:47 ` debbugs.el Stefan Monnier
2011-02-25 15:57 ` elpa.gnu.org packages in an Emacs checkout (was: debbugs.el) Ted Zlatanov
2011-02-25 17:49 ` elpa.gnu.org packages in an Emacs checkout Glenn Morris
2011-02-25 20:21 ` Ted Zlatanov
2011-02-25 20:34 ` Michael Albinus
2011-02-25 20:43 ` Glenn Morris [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=amei6v3kvw.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.com \
/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.