unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	65768@debbugs.gnu.org,
	Joseph Turner <joseph@breatheoutbreathe.in>
Subject: bug#65768: Bump persist.el version
Date: Fri, 12 Jan 2024 08:51:54 +0000	[thread overview]
Message-ID: <9d122a483ec1520aee0654b953aeb840@russet.org.uk> (raw)
In-Reply-To: <CADwFkmm=oomDWJoW+_HqaJnSg47HLXPc77JFbj-iqBUS74wK1g@mail.gmail.com>

On 2024-01-10 21:39, Stefan Kangas wrote:
> Joseph Turner <joseph@breatheoutbreathe.in> writes:
> 
>> Stefan Kangas <stefankangas@gmail.com> writes:
>> 
>>> Perhaps before releasing v0.6, it would make sense to update the
>>> Maintainer header comment to reflect that you're now the maintainer?
>>> If you agree, feel free to send a patch.
>> 
>> Sounds good!  Please see attached patches.
>> 
>> Thank you!
>> 
>> Joseph
> 
> Sorry for the belayed reply here.
> 
> I was about to install this, when I noticed that this package is
> actually maintained as an external package at:
> 
>     https://gitlab.com/phillord/persist
> 
> So I guess the easiest option is to continue running it externally,
> unless you want to move its maintenance to elpa.git, in which case we
> can arrange that.
> 
> If you want to maintain it externally, I guess Philip would either hand
> over that repository to you, or you would have to create a new one.
> 


I am very easy any way. If you want me to give full maintainer control 
to someone on the gitlab repo, just let me know. Or if you want to move 
the repo elsewhere or just use ELPA, then I will archive the gitlab 
repo.

Phil





  reply	other threads:[~2024-01-12  8:51 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
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 [this message]
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=9d122a483ec1520aee0654b953aeb840@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=65768@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=joseph@breatheoutbreathe.in \
    --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).