all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Payas Relekar <relekarpayas@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Magit
Date: Sat, 03 Sep 2022 20:05:36 +0530	[thread overview]
Message-ID: <875yi4cyi4.fsf@gmail.com> (raw)

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Akib Azmain Turja [2022-09-03 12:29:08] wrote:
>> Richard Stallman <rms@gnu.org> writes:
>>> 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`.
>

For what its worth, my 2c:

Magit is one of the _killer apps_ of Emacs. I was drawn by allure of
org-mode, but was hooked in with magit. I have ready fair number of
anecdotes with similar story and perhaps another equal number who use
Emacs exclusively for magit.

I am also not alone to say magit is the best git user interface in
existence, for many reasons, one of them being it uses Git's own idioms
and does not invent its own terminology like many others.

If maintaining org-mode outside Emacs and regularly merging it has been
managed so far, I am fairly certain it can be done with magit too. I am
fairly noob, but will be willing to take on the task to do it for magit
should it be included in core.

As for copyright, there are better people to discuss and resolve that
matter.

Regards,
Payas
--



             reply	other threads:[~2022-09-03 14:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-03 14:35 Payas Relekar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-04  4:13 Magit Payas Relekar
2022-09-04  5:25 ` Magit Eli Zaretskii
2022-09-04  5:51   ` Magit tomas
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             ` Magit Stefan Monnier
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 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
2010-02-28  0:41 magit Henri-Paul Indiogine
2010-02-28 14:32 ` magit Óscar Fuentes

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=875yi4cyi4.fsf@gmail.com \
    --to=relekarpayas@gmail.com \
    --cc=emacs-devel@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 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.