From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Akib Azmain Turja <akib@disroot.org>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: Magit
Date: Sat, 03 Sep 2022 10:20:23 -0400 [thread overview]
Message-ID: <jwv4jxo35my.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8735d93r9n.fsf@disroot.org> (Akib Azmain Turja's message of "Sat, 03 Sep 2022 12:29:08 +0600")
Akib Azmain Turja [2022-09-03 12:29:08] wrote:
> Richard Stallman <rms@gnu.org> writes:
>> [[[ To any NSA and FBI agents reading my email: please consider ]]]
>> [[[ whether defending the US Constitution against all enemies, ]]]
>> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>>
>> What is the situation with preparing to include Magit in Emacs?
>
> I don't think that will ever happen. Magit has many contributors, and
> many of them hasn't completed the paperwork. So including Magit in
> Emacs would be pretty hard (if possible)?
Actually, in a sense it's pretty easy: just make an exception for the
rule that all code needs to have its copyright assigned to the FSF.
Whether we want to make such an exception here of course is
another question.
But even if we do make such an exception, having a copy of Magit in
`emacs.git` would add extra maintenance burden to keep that copy in sync
with the one maintained elsewhere. So for administrative reasons, it's
probably preferable to keep it outside of `emacs.git`.
Stefan
next prev parent reply other threads:[~2022-09-03 14:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 5:41 Hunting the culprit package Pankaj Jangid
2022-08-31 12:25 ` Stefan Monnier
2022-08-31 17:20 ` Pankaj Jangid
2022-08-31 22:12 ` Stefan Monnier
2022-09-01 0:31 ` T.V Raman
2022-09-03 2:51 ` Magit Richard Stallman
2022-09-03 6:29 ` Magit Akib Azmain Turja
2022-09-03 14:20 ` Stefan Monnier [this message]
2022-09-03 14:56 ` Magit Eli Zaretskii
2022-09-03 18:22 ` Magit Akib Azmain Turja
2022-09-03 18:34 ` Magit Eli Zaretskii
2022-09-04 2:47 ` Magit Akib Azmain Turja
2022-09-04 5:16 ` Magit Eli Zaretskii
2022-09-03 15:16 ` Magit Stefan Kangas
2022-09-03 18:32 ` Magit Akib Azmain Turja
2022-09-03 18:51 ` Magit broken in NonGNU ELPA Stefan Kangas
2022-09-03 19:09 ` Magit Philip Kaludercic
2022-09-05 4:03 ` Magit Richard Stallman
2022-09-05 8:58 ` Magit Philip Kaludercic
2022-09-07 2:19 ` Magit Richard Stallman
2022-09-07 3:33 ` Magit Phil Sainty
2022-09-07 12:40 ` Magit Stefan Monnier
2022-09-07 13:02 ` Magit Akib Azmain Turja
2022-09-03 18:45 ` Magit Stefan Monnier
2022-09-05 4:03 ` Magit Richard Stallman
2022-09-05 9:04 ` Magit Philip Kaludercic
2022-09-05 11:48 ` Magit Eli Zaretskii
2022-09-07 2:19 ` Magit Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2022-09-03 14:35 Magit Payas Relekar
2022-09-04 4:13 Magit Payas Relekar
2022-09-04 5:25 ` Magit Eli Zaretskii
2022-09-04 5:51 ` Magit tomas
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=jwv4jxo35my.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=akib@disroot.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/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).