From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: Alexey Veretennikov <fourier@protonmail.ch>, emacs-devel@gnu.org
Subject: comint-mime and loccur update (was: [RFC] MIME attachments for comint)
Date: Mon, 18 Oct 2021 12:44:40 -0400 [thread overview]
Message-ID: <jwvilxu1e72.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87zgr6d9og.fsf@gmail.com> (Augusto Stoffel's message of "Mon, 18 Oct 2021 10:22:23 +0200")
Augusto Stoffel wrote:
> All right, let' add it "right now" then :-)
Done.
> I've made the necessary changes, but I guess I'll wait until Emacs 28 is
> out to make an official release, since the package depends on it.
Not in the mood for time travel, eh?
> PS: The loccur package is outdated on ELPA, could you pull the newest
> version? FWIW, I didn't get a reply from the maintainer when I asked if
> he wanted to have auto-sync, but I can report that he was careful to
> check that I have the CA papers before merging a patch from me.
Any chance someone could update the upstream loccur?
Currently, the upstream code and the elpa.git code have diverged:
Upstream of loccur has DIVERGED!
Local changes:
b232bc34d4 alexey.vereten.. * packages/loccur/loccur.el: Updated to version 1.2.4
ca9c2159f3 monnier@iro.um.. * packages/loccur/loccur.el (loccur, loccur-current): Autoload.
Upstream changes:
01b7afa625 fourier@proton.. Updated function names
2120345933 fourier@proton.. Updated version to 1.2.5
9cd6c9eb17 fourier@proton.. Merge pull request #14 from astoff/master
d4b286a0db fourier@proton.. Updated contribution information and added license
75bbd853d5 arstoffel@gmai.. Add loccur-isearch
284d7bb285 fourier@proton.. Added melpa badge
4934c0560d alexey.vereten.. Updated version and comments
099e8999b0 alexey.vereten.. Fixed issue #12
194d70e6be alexey.vereten.. Fixed issue #8
5650277d58 alexey.vereten.. Implemented solution for the issue #9.
650d91dda0 txm.fourier@gm.. Merge pull request #7 from syohex/fix-min-version
0e3234586d syohex@gmail.com Set minimum Emacs version
So, we'd need someone with write access to the upstream repo to merge
the b232bc34d4 and ca9c2159f3 commits into it (I don't know if the code
changes are still needed, but we do need the metadata to be merged so
that we can bring the upstream into elpa.git via a fast-forward).
Stefan
next prev parent reply other threads:[~2021-10-18 16:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 19:00 [RFC] MIME attachments for comint Augusto Stoffel
2021-09-27 20:37 ` Stefan Monnier
2021-09-28 16:05 ` Augusto Stoffel
2021-09-28 19:26 ` Stefan Monnier
2021-09-30 6:02 ` Richard Stallman
2021-09-30 7:09 ` Augusto Stoffel
2021-10-02 23:17 ` Richard Stallman
2021-10-03 7:48 ` Augusto Stoffel
2021-10-04 22:23 ` Richard Stallman
2021-09-30 8:49 ` Gregory Heytings
2021-10-04 22:25 ` Richard Stallman
2021-09-30 7:34 ` Colin Baxter
2021-09-28 5:36 ` Lars Ingebrigtsen
2021-09-28 16:09 ` Augusto Stoffel
2021-09-28 16:29 ` Robin Tarsiger
2021-09-28 18:22 ` Augusto Stoffel
2021-09-29 5:35 ` Lars Ingebrigtsen
2021-10-17 16:20 ` Stefan Monnier
2021-10-17 16:32 ` Stefan Monnier
2021-10-18 8:22 ` Augusto Stoffel
2021-10-18 16:44 ` Stefan Monnier [this message]
2021-10-20 12:17 ` comint-mime and loccur update (was: [RFC] MIME attachments for comint) Alexey Veretennikov
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=jwvilxu1e72.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=arstoffel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=fourier@protonmail.ch \
/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).