emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Bleeding edge in elpa
Date: Mon, 09 Mar 2015 10:08:58 +0100	[thread overview]
Message-ID: <86d24itu51.fsf@example.com> (raw)
In-Reply-To: CADdV=Ms6v3CGmXm2PE9vjDhxoRUeP9h7vY1UupGUj-FWdb42oQ@mail.gmail.com

Nikolai Weibull wrote:
> On Sat, Mar 7, 2015 at 3:47 PM, Xavier Maillard <xavier-U5RQyKqGfor/u5h4R/Qkbg@public.gmane.org> wrote:
>> Nikolai Weibull <now-yvQGvizXgks@public.gmane.org> writes:
>
>>> Would it be of interest to anyone else if the bleeding edge version
>>> was available via elpa?
>
>> Isn't it already available via M-x package interface ?
>
> No, only the version based on the maint branch is available via elpa.
>
>> I'd rather use git (I really do not like the package stuff).
>
> As Grant pointed out, it’s a lot more convenient working inside Emacs
> for switching between versions and such.

How do you switch between versions in ELPA?  IIUC, you only get the
latest version, and if that one is not right, you're kind of stuck: you
can't reinstall the previous version via the interface. Or maybe I have
to learn something new?

Best regards,
  Seb

-- 
Sebastien Vauban

  parent reply	other threads:[~2015-03-09  9:08 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07 14:36 Bleeding edge in elpa Nikolai Weibull
2015-03-07 14:47 ` Xavier Maillard
2015-03-07 16:09   ` Nikolai Weibull
2015-03-08  5:48     ` Xavier Maillard
2015-03-09  9:08     ` Sebastien Vauban [this message]
2015-03-09 16:24       ` T.F. Torrey
2015-03-07 15:40 ` Grant Rettke
2015-03-07 21:44 ` T.F. Torrey
2015-03-08  1:32 ` Nicolas Girard
2015-03-08 14:17 ` Aaron Ecay
2015-03-08 17:24   ` Nikolai Weibull
2015-03-08 17:59     ` Achim Gratz
2015-03-08 18:34       ` Nikolai Weibull
2015-03-08 18:59         ` Rasmus
2015-03-09  6:48           ` T.F. Torrey
2015-03-10  1:57             ` Aaron Ecay
2015-03-10 21:30               ` T.F. Torrey
2015-03-11  2:51                 ` Aaron Ecay
2015-03-11 19:18                   ` T.F. Torrey
2015-03-11 19:59                     ` Nick Dokos
2015-03-09  7:53       ` T.F. Torrey
2015-03-09 18:24         ` Achim Gratz
2015-03-09 19:21           ` T.F. Torrey
2015-03-10 11:01             ` Alexis
2015-03-10 15:21               ` Grant Rettke
2015-03-08 18:09   ` T.F. Torrey
2015-03-08 19:57     ` Rasmus
2015-03-08 20:20       ` Achim Gratz
2015-03-08 20:27         ` Rasmus
2015-03-08 20:36           ` Achim Gratz
2015-03-09  8:13         ` T.F. Torrey
2015-03-09  7:31       ` T.F. Torrey
2015-03-10  2:01         ` Richard Y. Kim
2015-03-10  6:29           ` Achim Gratz
2015-03-10 21:21             ` T.F. Torrey
2015-03-10 20:20           ` T.F. Torrey
2015-08-05  0:00   ` Bastien Guerry
2015-03-10 10:51 ` Steinar Bang
2015-03-10 17:11   ` Achim Gratz

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86d24itu51.fsf@example.com \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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/org-mode.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).