From: Julien Danjou <julien@danjou.info>
To: emacs-devel@gnu.org
Subject: Re: ELPA update
Date: Thu, 29 Sep 2011 12:14:22 +0200 [thread overview]
Message-ID: <87vcsbwt8h.fsf@keller.adm.naquadah.org> (raw)
In-Reply-To: <8739ffn3dl.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 29 Sep 2011 03:45:26 -0500")
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
On Thu, Sep 29 2011, Ted Zlatanov wrote:
> I don't see what's wrong with my proposal to have a `elpa-dev' branch
> for unstable and `elpa-stable' for stable packages; merging `elpa' into
> `elpa-dev' will be a much clearer sign to publish a new version than
> incrementing the version number (which, as we know, is often
> unparseable).
For the record, I am ok to do something more cmplex than the
commit->publish work flow, as far as it is (mostly) automatic and I
don't have to ping anyone to see my package online. :)
The problem I see with branch merging, is that you can't select a
precise package to merge in a flow of commit, unless you just do a merge
without keeping the history, which kind of sucks too.
(I'm more a git expert than a bzr one, but I don't think I'm breaking
assumption here).
--
Julien Danjou
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-09-29 10:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 14:25 ELPA update Julien Danjou
2011-09-27 15:53 ` Chong Yidong
2011-09-28 7:48 ` Julien Danjou
2011-09-28 8:41 ` Tassilo Horn
2011-09-28 14:05 ` Stefan Monnier
2011-09-28 17:30 ` Ted Zlatanov
2011-10-12 4:58 ` Stefan Monnier
2011-09-28 13:52 ` Ted Zlatanov
2011-09-28 14:00 ` Julien Danjou
2011-09-28 17:25 ` Ted Zlatanov
2011-09-28 17:28 ` Julien Danjou
2011-09-28 18:43 ` Ted Zlatanov
2011-09-28 20:58 ` Stefan Monnier
2011-09-28 23:01 ` PJ Weisberg
2011-09-29 1:16 ` Stephen J. Turnbull
2011-09-29 8:45 ` Ted Zlatanov
2011-09-29 10:14 ` Julien Danjou [this message]
2011-09-29 12:36 ` Ted Zlatanov
2011-09-29 14:09 ` Julien Danjou
2011-09-29 15:08 ` Ted Zlatanov
2011-09-29 12:26 ` Stephen J. Turnbull
2011-09-28 14:53 ` Eli Zaretskii
2011-09-29 7:43 ` Jambunathan K
2011-09-29 15:03 ` Stefan Monnier
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=87vcsbwt8h.fsf@keller.adm.naquadah.org \
--to=julien@danjou.info \
--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).