From: Protesilaos Stavrou <info@protesilaos.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, 46964@debbugs.gnu.org
Subject: bug#46964: [ELPA]: [PATCH] Replace modus-*-theme with modus-themes from :core
Date: Fri, 19 Mar 2021 16:18:21 +0200 [thread overview]
Message-ID: <8735wrtefm.fsf@protesilaos.com> (raw)
In-Reply-To: <jwvv99n8fy5.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 19 Mar 2021 08:55:03 -0400")
On 2021-03-19, 08:55 -0400, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> close 46964
> thanks
>
>> Thank you! The update went through. All good here. The final step
>> will be to remove the old packages. I guess we can do that in a new bug
>> report, say, six months from now. Feel free to close this one.
>
> Done.
Thanks!
>> On another note, is there some way I could use elpa-devel to distribute
>> the upstream version of my themes? Patching emacs.git on a daily basis
>> would not be feasible... While having a bleeding edge variant would
>> help with user testing, so that when I send a new tagged release to
>> emacs.git (every month or so), I can be confident that everything is in
>> order.
>
> Hmm... currently the GNU ELPA scripts can understand the situation where
> the release and the -devel code come from two different branches of the
> same repository, but having the release come from :core and the other
> from :url would require a fair bit of changes I think.
>
> I believe it would be easier in that case to make both the release and
> the -devel versions come from :url (and not use :core at all).
In that case, let's leave it as-is. I prefer to keep :core in place
because it is easier to prepare one patch for emacs.git and have it
trickle down to elpa.git.
--
Protesilaos Stavrou
protesilaos.com
prev parent reply other threads:[~2021-03-19 14:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 11:58 bug#46964: [ELPA]: [PATCH] Replace modus-*-theme with modus-themes from :core Protesilaos Stavrou
2021-03-06 14:39 ` Basil L. Contovounesios
2021-03-06 15:00 ` Stefan Monnier
2021-03-06 16:19 ` Protesilaos Stavrou
2021-03-06 18:35 ` Stefan Monnier
2021-03-07 7:32 ` Protesilaos Stavrou
2021-03-09 15:54 ` Basil L. Contovounesios
2021-03-09 16:46 ` Stefan Monnier
2021-03-09 19:08 ` Protesilaos Stavrou
2021-03-09 20:49 ` Stefan Monnier
2021-03-10 3:48 ` Stefan Monnier
2021-03-10 5:43 ` Protesilaos Stavrou
2021-03-10 18:41 ` Stefan Monnier
2021-03-10 20:13 ` Protesilaos Stavrou
2021-03-10 23:17 ` Stefan Monnier
2021-03-10 23:23 ` Basil L. Contovounesios
2021-03-11 3:07 ` Stefan Monnier
2021-03-11 8:27 ` Protesilaos Stavrou
2021-03-11 19:45 ` Basil L. Contovounesios
2021-03-11 22:54 ` Stefan Monnier
2021-03-12 7:59 ` Protesilaos Stavrou
2021-03-13 17:10 ` Stefan Monnier
2021-03-17 7:04 ` Protesilaos Stavrou
2021-03-18 7:55 ` Protesilaos Stavrou
2021-03-18 17:52 ` Stefan Monnier
2021-03-19 5:29 ` Protesilaos Stavrou
2021-03-19 12:55 ` Stefan Monnier
2021-03-19 14:18 ` Protesilaos Stavrou [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
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=8735wrtefm.fsf@protesilaos.com \
--to=info@protesilaos.com \
--cc=46964@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=monnier@iro.umontreal.ca \
/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).