From: Ken Manheimer <ken.manheimer@gmail.com>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] New package: multishell
Date: Mon, 4 Jan 2016 15:29:40 -0500 [thread overview]
Message-ID: <CAAT_zTH41aMKdAKtyjfkzdm=EpzE5LZt21UKxfp1+V1uD1xUYA@mail.gmail.com> (raw)
In-Reply-To: <CAAT_zTGZgQty9YpxaNY7em9RkZ_vMENqkg1ES=eV6aUik6arCg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
On Mon, Jan 4, 2016 at 1:49 PM, Ken Manheimer <ken.manheimer@gmail.com>
wrote:
> On Mon, Jan 4, 2016 at 1:27 PM, Artur Malabarba <bruce.connor.am@gmail.com
> > wrote:
>
>> I don't see any problem. The only thing that comes to mind is that, if
>> you don't want people to get used to the current version then you might
>> want to remove the package from Elpa for the moment.
>>
>> I'm not sure if setting the version number to 0 will do that, or if it'll
>> only prevent further updates.
>>
> Ah! I didn't think it was yet released to ELPA - I don't see it in the
> packages list. I'm uncertain whether or not you see that it actually is
> release - could you let me know whether or not it is, and if it is I'll
> move it aside, one way or another.
>
Never mind - I think I've settled the change, and pushed it to the
repository with a version number incremented so it should be released,
instead of any prior versions. I still don't know whether or not the
absence in list-packages means it wasn't already released, but that
shouldn't matter now that a ready version is in place.
[-- Attachment #2: Type: text/html, Size: 1830 bytes --]
next prev parent reply other threads:[~2016-01-04 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 22:19 [ELPA] New package: multishell Ken Manheimer
2016-01-03 20:26 ` Artur Malabarba
2016-01-04 17:07 ` Ken Manheimer
2016-01-04 18:27 ` Artur Malabarba
2016-01-04 18:49 ` Ken Manheimer
2016-01-04 20:29 ` Ken Manheimer [this message]
2016-01-05 3:23 ` Artur Malabarba
2016-01-05 3:42 ` Michael Heerdegen
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='CAAT_zTH41aMKdAKtyjfkzdm=EpzE5LZt21UKxfp1+V1uD1xUYA@mail.gmail.com' \
--to=ken.manheimer@gmail.com \
--cc=bruce.connor.am@gmail.com \
--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).