From: Lennart Borgman <lennart.borgman@gmail.com>
To: Sebastian Wiesner <lunaryorn@gmail.com>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: maintain flymake.el
Date: Mon, 16 Dec 2013 22:30:15 +0100 [thread overview]
Message-ID: <CANbX367utrHk5+NJEe=GXfZFw0Pa7z3KxCz_Auioh8qEcYTsiQ@mail.gmail.com> (raw)
In-Reply-To: <CALf2awQFSXUrjF--Eqr95R8=dUYFXTP653sMizkdKfn5vScAQQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
On Mon, Dec 16, 2013 at 7:24 PM, Sebastian Wiesner <lunaryorn@gmail.com>wrote:
> 2013/12/16 Glenn Morris <rgm@gnu.org>:
> > Sebastian Wiesner wrote:
> >
>
> I hope it makes clear that Flycheck likely won't ever be part of GNU
> Emacs, even though my personal motives are omitted.
>
> Please tell me if you find anything missing, or think, that it needs
> improvement.
>
> > This is the emacs-devel list, so "BTW, this mode will never be part of
> > Emacs" is kind of a big thing.
>
> I am well aware of where I am, and I assure you, that I would have
> prefered to never have to discuss this topic here.
>
> However, I was invited to this discussion, and asked this particular
> question. I answered it by courtesy, and I do not think that I
> deserve blame for an answer which you do not like.
>
>
I am glad for your contribution, Sebastian, but it is still troublesome if
the code is not GPL. I hope you do not mind me saying that. It is just a
matter of fact, nothing personal at all! ;-)
We have had a similar situation with php-mode. A lot of contributors and we
could not get every one to sign their contributions. It took me a long time
to try to get the people to sign and in the end I simply gave up. My
conclusion was that I could have been writing a much php-mode in much less
time than I used trying to fix this. However after this I did not find time
to do it any more.
And I do not have time to contribute now. Not even to discus, really. ;-)
I write this to you just to tell you that it is not a small problem. My
best wishes otherwise, and again thanks for contributing!
[-- Attachment #2: Type: text/html, Size: 2755 bytes --]
next prev parent reply other threads:[~2013-12-16 21:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 17:01 maintain flymake.el Leo Liu
2013-12-06 17:38 ` Stefan Monnier
2013-12-06 17:50 ` Ted Zlatanov
2013-12-07 2:21 ` Leo Liu
2013-12-14 21:23 ` Sebastian Wiesner
2013-12-15 18:31 ` Sebastian Wiesner
2013-12-16 14:32 ` Ted Zlatanov
2013-12-16 16:06 ` Jan Djärv
2013-12-16 16:48 ` Sebastian Wiesner
2013-12-16 18:30 ` Jan Djärv
2013-12-16 19:03 ` Sebastian Wiesner
2013-12-16 16:57 ` Sebastian Wiesner
2013-12-16 17:26 ` Glenn Morris
2013-12-16 18:24 ` Sebastian Wiesner
2013-12-16 20:55 ` Glenn Morris
2013-12-16 21:00 ` Sebastian Wiesner
2013-12-16 21:30 ` Lennart Borgman [this message]
2013-12-16 21:52 ` Glenn Morris
2013-12-16 17:28 ` Ted Zlatanov
2013-12-17 0:12 ` Leo Liu
2013-12-17 0:02 ` Leo Liu
2013-12-17 6:37 ` Arne Jørgensen
2013-12-17 15:45 ` Leo Liu
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='CANbX367utrHk5+NJEe=GXfZFw0Pa7z3KxCz_Auioh8qEcYTsiQ@mail.gmail.com' \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=lunaryorn@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).