From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: SOLVED
Date: Thu, 05 May 2016 16:10:06 +0000 [thread overview]
Message-ID: <874mac5vvl.fsf@mat.ucm.es> (raw)
In-Reply-To: CAFyQvY0-gMVfOTbCvCm7JUZEf2NaWKkfn-EDk2MSM_WTvJVKQw@mail.gmail.com
>>> "Kaushal" == Kaushal Modi <kaushal.modi@gmail.com> writes:
> , but not sure about the structure of
> that patch
> (which git diff option to use
> - You first need to rebase your local git area to emacs-25 as you are
> planning to provide just a documentation patch, (otherwise you would
> rebase to the master branch).
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?
> - Then git commit the changes in your local area.
> - http://git.savannah.gnu.org/cgit/emacs.git/plain/CONTRIBUTE has
> instructions on the style of writing commit logs.
> - Use git format_patch HEAD~1 to create patch for that last commit.
Ok thanks
> , to whom to send that patch
> - You use the same M-x report-emacs-bug to describe the problem you
> are solving along with the inline pasted patch you just created.
> etc).
> While you are at it, you can even initiate the process to finish the
> copyright paperwork if you'd like to contribute more in future (why
> not! :)); even though you don't need that right now for 3 lines of
> documentation patch.
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
> I see that you heavily contribute to matlab-mode.el. Thanks for
> maintaining that!
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.
> And as Stefan Monnier mentioned in an earlier email
> thread, that could possibly be integrated into octave-mode.el piece
> by piece and be part of Emacs.
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.
> Hope this helps.
> --
Yes it did thanks.
Uwe
next prev parent reply other threads:[~2016-05-05 16:10 UTC|newest]
Thread overview: 20+ 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 ` Uwe Brauer [this message]
2016-05-05 16:18 ` SOLVED Kaushal Modi
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
-- strict thread matches above, loose matches on Subject: below --
2012-01-28 20:20 Xemacs: org-preview-latex-fragment, png not readable Uwe Brauer
2012-01-28 20:59 ` Solved (was: Xemacs: org-preview-latex-fragment, png not readable.) Uwe Brauer
2012-01-28 22:33 ` Solved Bastien
2012-01-29 0:13 ` Solved Nick Dokos
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=874mac5vvl.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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.