From: Philip Kaludercic <philipk@posteo.net>
To: Jijun Ma <jijun.ma@hotmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [ELPA] New package: pdf-view-pagemark
Date: Fri, 12 May 2023 05:52:00 +0000 [thread overview]
Message-ID: <87ilcyxfjz.fsf@posteo.net> (raw)
In-Reply-To: <TY2PR03MB390259B41210A21C158C71109F779@TY2PR03MB3902.apcprd03.prod.outlook.com> (Jijun Ma's message of "Wed, 10 May 2023 22:10:21 +0000")
Jijun Ma <jijun.ma@hotmail.com> writes:
> Thanks!
> Now I've signed the FSF CA.
While this is being proceed, I'd like question why you think that this
your package is better distributed separately? Taking a look at the
code, modulo user options, helper functions and other decoration the
main functionality boils down to a single function. Is it really worth
the maintainer-overhead to distribute this separately? Have you
communicated with the upstream developers on the matter?
> -----Original Message-----
> From: Eli Zaretskii <eliz@gnu.org>
> Sent: Wednesday, May 10, 2023 7:25 PM
> To: Philip Kaludercic <philipk@posteo.net>
> Cc: jijun.ma@hotmail.com; emacs-devel@gnu.org
> Subject: Re: [ELPA] New package: pdf-view-pagemark
>
>> From: Philip Kaludercic <philipk@posteo.net>
>> Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>, "'Eli Zaretskii'"
>> <eliz@gnu.org>
>> Date: Wed, 10 May 2023 06:42:49 +0000
>>
>> Jijun Ma <jijun.ma@hotmail.com> writes:
>>
>> > That's a feature not strongly part of pdf-tools, better to be an extension.
>> > I've not signed FSF CA yet. How can I sign?
>>
>> I don't have a copy of the form, Eli can send them to you.
>
> Form sent off-list.
prev parent reply other threads:[~2023-05-12 5:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 12:43 [ELPA] New package: pdf-view-pagemark Jijun Ma
2023-05-08 20:23 ` Philip Kaludercic
2023-05-08 21:30 ` Jijun Ma
2023-05-09 8:46 ` Philip Kaludercic
2023-05-09 8:49 ` Jijun Ma
2023-05-10 6:42 ` Philip Kaludercic
2023-05-10 11:25 ` Eli Zaretskii
2023-05-10 22:10 ` Jijun Ma
2023-05-12 5:52 ` Philip Kaludercic [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=87ilcyxfjz.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jijun.ma@hotmail.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).