all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: emacs-devel@gnu.org, "Stefan Monnier" <monnier@iro.umontreal.ca>,
	"Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Subject: Re: Upcoming merge of adaptive-wrap
Date: Thu, 25 Jan 2024 19:32:07 +0800	[thread overview]
Message-ID: <87bk99ps20.fsf@yahoo.com> (raw)
In-Reply-To: <87ede5u3yd.fsf@gmx.net> (Stephen Berman's message of "Thu, 25 Jan 2024 11:01:30 +0100")

Stephen Berman <stephen.berman@gmx.net> writes:

> Sorry for not responding to your message from last August 10, which I
> have just found again; FWIW I have these excuses for my negligence:
> First, I was on vacation at the time and didn't see the message till
> around two weeks later.  Second, you wrote in that message:
>
>> Stefan, what do you say to this?  Since the package in ELPA, migrating
>> it into Emacs should not pose any legal difficulties, so the only
>> prerequisites are suitable entries in NEWS and the documentation,
>> correct?
>
> From this I thought you were addressing Stefan Monnier, who is nominally
> the co-author of the package (but actually is responsible for the most
> important part of the implementation).

I think I was addressing Stefan Kangas at the time, not you.  But I
could be mistaken.  I'm glad this misunderstanding is over with.

> Third, I didn't know (or had forgotten) that I'm still listed as
> maintainer of the package, a role that I've not wanted to have for a
> long time.  In fact, in a private exchange in June 2020 as followup to
> bug#41810, Stefan asked Kévin Le Gouguec if he would like to assume
> the maintainership, though AFAIK neither that question nor the bug
> report have been resolved; I've added both to the Cc:.
>
> In any case, I have no objection to moving adaptive-wrap from GNU ELPA
> to Emacs core; but whatever the outcome, I would like to be removed as
> maintainer.

OK, then the merge will take place in a few days, provided that no other
objections arise.



  reply	other threads:[~2024-01-25 11:32 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <878r4eqjh8.fsf.ref@yahoo.com>
2024-01-25  1:39 ` Upcoming merge of adaptive-wrap Po Lu
2024-01-25  4:44   ` Adam Porter
2024-01-25 10:01   ` Stephen Berman
2024-01-25 11:32     ` Po Lu [this message]
2024-01-25 12:37       ` Eli Zaretskii
2024-01-25 13:15         ` Po Lu
2024-01-26  8:05     ` Kévin Le Gouguec
2024-01-26 10:21       ` Po Lu
2024-01-26 11:26       ` Joost Kremers
2024-01-26 12:40         ` Eli Zaretskii
2024-01-26 13:47           ` Joost Kremers
2024-01-31 19:18             ` Stefan Monnier
2024-02-02  4:41               ` Madhu
2024-02-02  7:22                 ` Eli Zaretskii
2024-01-25 17:10   ` Dmitry Gutov
2024-01-25 20:01     ` Stefan Kangas
2024-01-25 20:11       ` Dmitry Gutov
2024-01-26  1:45     ` Po Lu
2024-01-26  2:08       ` Dmitry Gutov
2024-01-26  2:22         ` Po Lu
2024-01-26  2:30           ` Dmitry Gutov
2024-01-26  4:03             ` Po Lu
2024-01-27  1:44               ` Dmitry Gutov
2024-01-27  3:58                 ` Po Lu
2024-01-27 16:56                   ` Dmitry Gutov
2024-01-27 22:59                     ` Stefan Kangas
2024-01-28  0:18                       ` [External] : " Drew Adams
2024-01-28  9:02                         ` Michael Albinus
2024-01-28  9:36                           ` Po Lu
2024-01-28 13:03                             ` Dmitry Gutov
2024-01-29  1:56                               ` Po Lu
2024-01-28 15:32                           ` Drew Adams
2024-01-28  9:34                     ` Po Lu
2024-01-28 13:11                       ` Dmitry Gutov
2024-01-28 14:25                         ` Po Lu
2024-01-28 18:01                           ` Dmitry Gutov
2024-01-29  1:55                             ` Po Lu
2024-01-26  1:54     ` Po Lu
2024-01-26  7:50       ` Eli Zaretskii
2024-01-26 10:24         ` Po Lu
2024-01-25 20:05   ` Stefan Kangas

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bk99ps20.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=kevin.legouguec@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=stephen.berman@gmx.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.