unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Joseph Turner <joseph@breatheoutbreathe.in> Joseph Turner via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: phillip.lord@russet.org.uk
Cc: Eli Zaretskii <eliz@gnu.org>,
	Stefan Kangas <stefankangas@gmail.com>,
	65768@debbugs.gnu.org
Subject: bug#65768: Bump persist.el version
Date: Tue, 31 Oct 2023 08:41:55 -0700	[thread overview]
Message-ID: <87ttq6u5lu.fsf@breatheoutbreathe.in> (raw)
In-Reply-To: <e7e289b97f52a4a4ee03b96e7ff8eb8e@russet.org.uk>

Hi Phillip!

phillip.lord@russet.org.uk writes:

> Oh dear, you have had to ping on this many times.

No worries :)

> Would you be interested in taking over maintainership of persist? I am
> very short of Emacs time these days.

Yes, I am interested!  Stefan, Eli, what do you think?

Stefan, before I commit to maintainership of persist, please let me know
of any maintainer guidelines I should be aware of.  I have read
emacs/CONTRIBUTE and elpa/README.  Would persist.el maintainership
require subscribing to the mailing list?

Thank you!

Joseph





  reply	other threads:[~2023-10-31 15:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06  2:13 bug#65768: Bump persist.el version Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-06 16:39 ` Stefan Kangas
2023-09-16 22:28   ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-30 14:30     ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-30 20:54   ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-31 12:07     ` phillip.lord
2023-10-31 15:41       ` Joseph Turner [this message]
2023-10-31 16:43         ` Eli Zaretskii
2023-10-31 17:05           ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-01  0:34             ` Stefan Kangas
2023-11-12  4:26               ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-10 21:39                 ` Stefan Kangas
2024-01-12  8:51                   ` phillip.lord
2024-01-12  9:15                     ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 13:10                       ` phillip.lord
2024-01-13  9:41                       ` Stefan Kangas
2024-01-13 19:14                         ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-13  9:45                       ` Stefan Kangas
2024-01-13 19:15                         ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-06 20:38             ` phillip.lord
2023-11-12  4:27               ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87ttq6u5lu.fsf@breatheoutbreathe.in \
    --to=joseph@breatheoutbreathe.in \
    --cc=65768@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=phillip.lord@russet.org.uk \
    --cc=stefankangas@gmail.com \
    /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).