From: Philip Kaludercic <philipk@posteo.net>
To: Chmouel Boudjnah <chmouel@chmouel.com>
Cc: Stefan Kangas <stefankangas@gmail.com>, emacs-devel@gnu.org
Subject: Re: [NonGnu ELPA] New package: flymake-codespell
Date: Tue, 31 Oct 2023 08:29:29 +0000 [thread overview]
Message-ID: <87h6m7w5xy.fsf@posteo.net> (raw)
In-Reply-To: <CAKSXASQaqj=5PxF2Bkqfqf-36Z7sUDfg9BdvZsDqbTdQmByRKQ@mail.gmail.com> (Chmouel Boudjnah's message of "Mon, 30 Oct 2023 04:59:24 +0100")
Chmouel Boudjnah <chmouel@chmouel.com> writes:
> On Sun, Oct 29, 2023 at 11:41 PM Stefan Kangas <stefankangas@gmail.com>
> wrote:
>
>> I didn't take a look at it, but I have had something similar cooking for
>> a while:
>>
>> https://github.com/skangas/flymake-codespell
>>
>> How do you feel about merging our efforts? It would be better with just
>> one package for this, for obvious reasons. I don't really care which
>> package to use as a base, but I do think it would be better to keep the
>> result on GNU ELPA.
>>
>
> This is great, I didn't see this before.
>
> Your package seems a bit better documented and configurable, I would not
> mind deprecating mine and just put a notice on the repository to have users
> (but I doubt i have many) redirected to your's.
>
> (and I guess maybe to have a submission of your's for GNU ELPA ?)
Should we go ahead and add Stefan's package then?
> Cheers,
> Chmouel
>
>
>
>
>> Please let me know what you think.
>>
--
Philip Kaludercic
next prev parent reply other threads:[~2023-10-31 8:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 13:45 [NonGnu ELPA] New package: flymake-codespell Chmouel Boudjnah
2023-10-29 22:40 ` Stefan Kangas
2023-10-30 3:59 ` Chmouel Boudjnah
2023-10-31 8:29 ` Philip Kaludercic [this message]
2023-10-31 11:49 ` Stefan Kangas
2023-10-31 11:53 ` Chmouel Boudjnah
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=87h6m7w5xy.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=chmouel@chmouel.com \
--cc=emacs-devel@gnu.org \
--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).