all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Ted Zlatanov <tzz@lifelogs.com>, emacs-devel@gnu.org
Subject: Re: How does ELPA work?
Date: Tue, 08 Mar 2011 20:52:05 +0100	[thread overview]
Message-ID: <87r5ahqtju.fsf@gmx.de> (raw)
In-Reply-To: <877hc95um3.fsf@stupidchicken.com> (Chong Yidong's message of "Tue, 08 Mar 2011 13:34:44 -0500")

Chong Yidong <cyd@stupidchicken.com> writes:

>> 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.

Likely, I will add a ChangeLog. I do expect also contributions from
Evgeny Zubok (he is finishing his paperwork with the FSF), who has no
write access to the Emacs repository. This would simplify my life
committing his patches :-)

Thanks for all your support, and best regards, Michael.



      parent reply	other threads:[~2011-03-08 19:52 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
2011-03-08 18:48                   ` Ted Zlatanov
2011-03-08 19:52                   ` Michael Albinus [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=87r5ahqtju.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=cyd@stupidchicken.com \
    --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.