From: Kaushal Modi <kaushal.modi@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: SOLVED
Date: Thu, 05 May 2016 16:18:53 +0000 [thread overview]
Message-ID: <CAFyQvY1NJ-WqU3LwJGtLEX3QRvOuO501ZV6seJLVPKPidbFYqg@mail.gmail.com> (raw)
In-Reply-To: <874mac5vvl.fsf@mat.ucm.es>
[-- Attachment #1: Type: text/plain, Size: 1884 bytes --]
>
> I am a bit confused now, I cloned originally via
>
> git clone git://git.savannah.gnu.org/emacs.git
>
> And then ever pulled from it from time to time. That is what?, master or
> emacs-25?
>
By default the origin/master will be cloned.
I use the below to FORCE update to emacs-25
git fetch --all
git checkout origin/emacs-25
git reset --hard origin/emacs-25
Right, I wanted to wait till I am again in Germany, since I could to it
> electronically while I can't while I am in Spain, progress, sigh
>
Cool!
Ah well, I provided some functionality but I think the person who really
> contributed heavily to matlab-mode.el is Eric Ludlam, who unfortunately
> is too busy to maintain matlab-mode.el, so I just stepped in.
>
Thanks though for keeping the maintenance alive.
Ah well there are two problems with that:
>
> - a technical one. The real difference between these two packages
> IMHO is their shell. The relevant matlab code was written over a
> very long period of time (starting in 91), is very matlab
> specific and looks very complicated to me. I am not really sure
> that anyone besides Eric understands it.
>
> - a copyright issue. I did not discuss this in detail on this list,
> but RMS asked me why the code could not be in ELPA instead of
> being in MELPA and the reason is that MathWorks has some
> copyright over some parts of the code and it is very very
> unlikely that they will transfer that copyright to the FSF. The
> code is under GPL2+ though.
Understood. matlab-mode.el was just an example. I used to express that once
you have the copyright paperwork, it's much easier to contribute to Emacs
:) But it's great that you are already looking into it.
--
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 2921 bytes --]
next prev parent reply other threads:[~2016-05-05 16:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 20:01 vc-hg modeline changed Uwe Brauer
2016-05-05 9:15 ` SOLVED (was: vc-hg modeline changed.) Uwe Brauer
2016-05-05 11:26 ` Kaushal Modi
2016-05-05 16:10 ` SOLVED Uwe Brauer
2016-05-05 16:18 ` Kaushal Modi [this message]
2016-05-05 16:41 ` SOLVED Andreas Schwab
2016-05-05 20:12 ` SOLVED Uwe Brauer
2016-05-06 6:27 ` SOLVED Eli Zaretskii
2016-05-05 20:50 ` SOLVED Uwe Brauer
2016-05-05 21:33 ` SOLVED Kaushal Modi
2016-05-06 7:53 ` SOLVED Uwe Brauer
2016-05-06 9:28 ` SOLVED Yuri Khan
2016-05-06 10:29 ` SOLVED Uwe Brauer
2016-05-06 10:45 ` SOLVED II (was: SOLVED) Uwe Brauer
2016-05-06 12:10 ` SOLVED Clément Pit--Claudel
2016-05-06 12:24 ` SOLVED Yuri Khan
2016-05-06 12:32 ` SOLVED Clément Pit--Claudel
2016-05-06 13:00 ` SOLVED Eli Zaretskii
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=CAFyQvY1NJ-WqU3LwJGtLEX3QRvOuO501ZV6seJLVPKPidbFYqg@mail.gmail.com \
--to=kaushal.modi@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 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).