From: Lars Ingebrigtsen <larsi@gnus.org>
To: Toby Cubitt <tsc25@cantab.net>
Cc: Alex Branham <alex.branham@gmail.com>,
30235@debbugs.gnu.org, toby-undo-tree@dr-qubit.org
Subject: bug#30235: [patch] undo-tree byte-compiler warnings
Date: Wed, 18 Sep 2019 15:53:49 +0200 [thread overview]
Message-ID: <878sqllngy.fsf@gnus.org> (raw)
In-Reply-To: <E5F5388E-54B4-440B-8B5F-08F0D0F621C6@dr-qubit.org> (Toby Cubitt's message of "Wed, 18 Sep 2019 12:51:46 +0100")
Toby Cubitt <tsc25@cantab.net> writes:
> Not opposed to this at all! (I forgot what i said previously, but if I
> was then it was before I knew of the _ method.) Indeed, I think I
> already made exactly this change a while back in the undo-tree
> development repo, but maybe forgot to transfer this into ELPA.
Oh, OK. :-)
> Undo-tree went into ELPA before there was support for separate
> per-package git repos in ELPA, which is why this isn't automatic. It
> makes upstreaming changes from my development repo(s) to ELPA that bit
> more complicated than a simple git push. I'm very busy with real life
> these days, so this inevitably gets forgotten/postponed. Maybe this is
> a good opportunity to shift all my ELPA packages over to per-package
> git repos, so I can just make the ELPA repos upstreams of my package
> development repos?
Sounds like a good idea.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-09-18 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 23:18 bug#30235: [patch] undo-tree byte-compiler warnings Alex Branham
2019-06-25 11:51 ` bug#24354: " Lars Ingebrigtsen
2019-06-25 13:32 ` Basil L. Contovounesios
2019-06-25 13:34 ` Lars Ingebrigtsen
2019-06-26 3:24 ` bug#24354: " Richard Stallman
2019-09-17 12:39 ` Lars Ingebrigtsen
2019-09-18 11:51 ` Toby Cubitt
2019-09-18 13:53 ` Lars Ingebrigtsen [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=878sqllngy.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=30235@debbugs.gnu.org \
--cc=alex.branham@gmail.com \
--cc=toby-undo-tree@dr-qubit.org \
--cc=tsc25@cantab.net \
/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).