From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-devel@gnu.org
Subject: Re: Supporting multiline Package-Requires header
Date: Tue, 25 Aug 2015 07:44:08 +0200 [thread overview]
Message-ID: <87mvxfsz13.fsf@Rainer.invalid> (raw)
In-Reply-To: CAAdUY-LoS3j+Onw1S9_8hzC=Dx1sXCiUPQFY-tQymWDGaMjFBA@mail.gmail.com
Artur Malabarba writes:
> From what I've been gathering (do correct me if I'm wrong), it sounds
> like this issue stems from wanting to use GNU Elpa to release org
> snapshots.
Org snapshots are yet a different thing and trace the master branch.
> You want your version numbers to be updated every day, and you need
> that because you want to always deliver the very latest commits.
The maint branch is for bugfixes between releases, so the ELPA package
is for people that want releases plus bugfixes.
> However, the Gelpa reporistory is really more designed to deliver
> proper releases, not snapshots. Which is why its release system is
> based on when you bump the version number (which people usually do on
> a specific commit when they decide to release).
That's the design problem, it should really be based on tags instead.
Among other things, it allows you to release a version further down the
history, after proper testing, when (likely someone else) has already
added new commits on top of that already, which is common in distributed
development.
> That said, I'm not here to tell people they're "doing it wrong". And
> I'm very sympathetic to org.
> So, if you guys find that any solution on org's side would be "a
> horrible hack", I can put some effort into making Gelpa's "tiny hack"
> a little smaller.
We can cope, I just need direction as to what the decision is.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2015-08-25 5:44 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 11:12 Supporting multiline Package-Requires header Artur Malabarba
2015-08-10 11:42 ` Kaushal
2015-08-10 11:59 ` Artur Malabarba
2015-08-10 12:05 ` Phillip Lord
2015-08-10 12:28 ` Artur Malabarba
2015-08-10 12:51 ` Phillip Lord
2015-08-10 13:08 ` Artur Malabarba
2015-08-10 13:54 ` Bozhidar Batsov
2015-08-10 15:22 ` Artur Malabarba
2015-08-11 21:05 ` Phillip Lord
2015-08-11 21:48 ` Artur Malabarba
2015-08-12 5:34 ` Bozhidar Batsov
2015-08-12 14:09 ` Stefan Monnier
2015-08-12 14:23 ` Artur Malabarba
2015-08-12 17:18 ` Stefan Monnier
2015-08-12 20:10 ` Artur Malabarba
2015-08-13 18:13 ` Artur Malabarba
2015-08-13 20:44 ` Stefan Monnier
2015-08-13 22:37 ` Rasmus
2015-08-13 23:01 ` Artur Malabarba
2015-08-14 0:12 ` Rasmus
2015-08-14 1:42 ` Stefan Monnier
2015-08-17 18:45 ` Achim Gratz
2015-08-18 15:56 ` Stefan Monnier
2015-08-18 18:00 ` Achim Gratz
2015-08-19 17:14 ` Stefan Monnier
2015-08-23 6:33 ` Achim Gratz
2015-08-23 9:17 ` Artur Malabarba
2015-08-23 9:37 ` Achim Gratz
2015-08-23 12:03 ` Artur Malabarba
2015-08-23 22:17 ` Stefan Monnier
2015-08-23 22:12 ` Stefan Monnier
2015-08-23 23:32 ` Artur Malabarba
2015-08-23 22:16 ` Stefan Monnier
2015-08-24 6:56 ` Achim Gratz
2015-08-24 19:17 ` Stefan Monnier
2015-08-24 19:32 ` Achim Gratz
2015-08-24 22:51 ` Artur Malabarba
2015-08-25 5:44 ` Achim Gratz [this message]
2015-08-10 14:26 ` Thierry Volpiatto
2015-08-10 15:18 ` Artur Malabarba
2015-08-10 15:38 ` Thierry Volpiatto
2015-08-10 15:53 ` Artur Malabarba
2015-08-10 16:33 ` Thierry Volpiatto
2015-08-10 15:40 ` Nicolas Richard
2015-08-10 15:49 ` Artur Malabarba
2015-08-11 8:44 ` Nicolas Richard
2015-08-11 9:28 ` Artur Malabarba
2015-08-11 9:33 ` Nicolas Richard
2015-08-10 16:34 ` Thierry Volpiatto
2015-08-10 21:49 ` Phillip Lord
2015-08-11 9:24 ` Artur Malabarba
2015-08-10 22:05 ` Stefan Monnier
2015-08-11 8:56 ` Thierry Volpiatto
2015-08-11 15:55 ` Stefan Monnier
2015-08-10 22:01 ` Stefan Monnier
2015-08-11 9:29 ` Artur Malabarba
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=87mvxfsz13.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).