From: Chong Yidong <cyd@stupidchicken.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Ted Zlatanov <tzz@lifelogs.com>, emacs-devel@gnu.org
Subject: Re: How does ELPA work?
Date: Tue, 08 Mar 2011 13:34:44 -0500 [thread overview]
Message-ID: <877hc95um3.fsf@stupidchicken.com> (raw)
In-Reply-To: <87vcztqywb.fsf@gmx.de> (Michael Albinus's message of "Tue, 08 Mar 2011 18:56:36 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
>> The elpa bzr branch works a bit differently. There we keep the packages
>> in extracted (source) form, because the elpa branch does not itself
>> function as a package archive. Instead, we run a script to deploy the
>> package archive from it.
>
> Is it correct to continue updating this branch from now on?
Yes. Just make the changes directly in debbugs-0.1. For now, it's OK
for the contents of packages in the archive to be mutable, instead of
requiring a new package version for each change. We can revisit this as
Emacs 24 gets closer to release.
> If yes, where shall I document changes? ChangeLog in
> packages/debbugs-0.1?
We don't have a chagelog policy on the elpa branch, so it is OK to use
just bzr commit logs if you like. If you personally want to add a
ChangeLog or maintain a log in in debbugs.el, feel free.
next prev parent reply other threads:[~2011-03-08 18:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 9:30 How does ELPA work? joakim
2011-03-02 14:41 ` Ted Zlatanov
2011-03-05 21:09 ` Michael Albinus
2011-03-05 21:24 ` Chong Yidong
2011-03-06 22:05 ` Chong Yidong
2011-03-07 14:12 ` Michael Albinus
2011-03-08 0:25 ` Chong Yidong
2011-03-08 3:03 ` Stefan Monnier
2011-03-08 17:11 ` Chong Yidong
2011-03-08 13:03 ` Michael Albinus
2011-03-08 17:09 ` Chong Yidong
2011-03-08 17:56 ` Michael Albinus
2011-03-08 18:34 ` Chong Yidong [this message]
2011-03-08 18:48 ` Ted Zlatanov
2011-03-08 19:52 ` Michael Albinus
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=877hc95um3.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--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.