From: lee <lee@yun.yagibdah.de>
To: help-gnu-emacs@gnu.org
Subject: Re: How to propose an emacs patch (Re: replacing a function with another one)
Date: Mon, 17 Mar 2014 05:35:15 +0100 [thread overview]
Message-ID: <87iord1lz0.fsf@yun.yagibdah.de> (raw)
In-Reply-To: <878usaltfz.fsf@gmail.com> (Jambunathan K.'s message of "Sun, 16 Mar 2014 08:51:20 +0530")
Jambunathan K <kjambunathan@gmail.com> writes:
> lee <lee@yun.yagibdah.de> writes:
>
>>> Where there is a will there is a way.
>>
>> Asking here how best to go about it is a start ... It seems they need
>> some sort of paperwork from contributers for copyright reasons, and I
>> don`t know how to propose a patch or if such paperwork is needed for
>> that.
>
> You need to come to emacs-devel.
Hm, can`t hurt to subscribe :)
> Second best option is to put it on emacs-bugs.
I just did so --- I didn`t see your post earlier.
> Just say that you are proposing a patch and would like to
> have it as part of Emacs. Folks there will do the rest.
We`ll see --- I might have some mistakes in it because I don`t know
any better. It works fine for me, though and I hope they take it in.
You can try it out if you like: https://github.com/lee-/emacs/tree/master/hi-lock
> Remember you don't need to clone the repo for proposing a patch. You
> download JUST the relevant file from the Web Interface. You make a copy
> of it and make changes to it. And then submit the diff between the
> files.
Yes, I sent a diff. I`ve been updating and compiling from bzr every now
and then, so I switched to git and cloned the whole repo. I get much
better along with git.
> emacs-devel:
> emacs-bugs:
> emacs-sources.
I`m subscribed to emacs-bugs since a while; I`ll get the others, too.
--
Knowledge is volatile and fluid. Software is power.
next prev parent reply other threads:[~2014-03-17 4:35 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-08 19:43 replacing a function with another one lee
2014-03-08 19:54 ` Eli Zaretskii
2014-03-09 1:17 ` lee
2014-03-08 22:30 ` Michael Heerdegen
2014-03-09 17:58 ` lee
2014-03-09 19:10 ` Michael Heerdegen
2014-03-09 20:57 ` lee
2014-03-09 22:02 ` Michael Heerdegen
2014-03-10 0:53 ` lee
2014-03-10 2:18 ` Michael Heerdegen
2014-03-10 15:29 ` lee
2014-03-11 0:03 ` Michael Heerdegen
2014-03-11 13:34 ` lee
2014-03-11 23:40 ` Michael Heerdegen
2014-03-12 6:11 ` Michael Heerdegen
2014-03-12 7:07 ` Michael Heerdegen
2014-03-12 14:48 ` lee
2014-03-13 7:19 ` Michael Heerdegen
2014-03-15 19:51 ` lee
2014-03-17 12:00 ` Michael Heerdegen
2014-03-12 14:04 ` lee
2014-03-12 18:26 ` Stefan Monnier
2014-03-12 4:10 ` Michael Heerdegen
2014-03-10 12:44 ` Stefan Monnier
2014-03-10 23:35 ` lee
2014-03-11 0:41 ` Michael Heerdegen
2014-03-11 1:45 ` Michael Heerdegen
2014-03-11 19:05 ` lee
2014-03-11 22:58 ` Michael Heerdegen
2014-03-12 15:11 ` lee
2014-03-12 18:15 ` Stefan Monnier
2014-03-12 21:43 ` lee
2014-03-13 7:22 ` Michael Heerdegen
2014-03-15 20:02 ` lee
2014-03-11 4:11 ` lee
2014-03-11 5:01 ` Michael Heerdegen
2014-03-11 14:25 ` lee
2014-03-11 23:51 ` Michael Heerdegen
2014-03-12 15:22 ` lee
2014-03-13 7:33 ` Michael Heerdegen
2014-03-13 12:29 ` Stefan Monnier
2014-03-15 20:05 ` lee
2014-03-16 17:20 ` Stefan
2014-03-11 6:51 ` Michael Heerdegen
2014-03-11 15:41 ` lee
2014-03-11 23:21 ` Michael Heerdegen
2014-03-12 17:33 ` lee
2014-03-12 19:34 ` Florian Beck
2014-03-12 19:51 ` Florian Beck
2014-03-13 7:54 ` Michael Heerdegen
2014-03-15 20:14 ` lee
2014-03-12 12:45 ` Stefan Monnier
2014-03-12 17:42 ` lee
2014-03-13 2:43 ` Jambunathan K
2014-03-15 20:17 ` How to propose an emacs patch (Re: replacing a function with another one) lee
2014-03-16 3:21 ` Jambunathan K
2014-03-17 4:35 ` lee [this message]
2014-03-10 13:45 ` replacing a function with another one lee
2014-03-10 23:31 ` Michael Heerdegen
2014-03-12 13:16 ` Jambunathan K
2014-03-12 13:18 ` Jambunathan K
2014-03-15 20:22 ` lee
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=87iord1lz0.fsf@yun.yagibdah.de \
--to=lee@yun.yagibdah.de \
--cc=help-gnu-emacs@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.