From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: lee Newsgroups: gmane.emacs.help Subject: How to propose an emacs patch (Re: replacing a function with another one) Date: Sat, 15 Mar 2014 21:17:37 +0100 Organization: my virtual residence Message-ID: <87r463usgu.fsf_-_@yun.yagibdah.de> References: <87vbvofsi6.fsf@yun.yagibdah.de> <87bnxgs4r9.fsf@web.de> <87lhwj1cfz.fsf@yun.yagibdah.de> <87zjkz6vd5.fsf@web.de> <8738ir161u.fsf@yun.yagibdah.de> <87eh2b6nfm.fsf@web.de> <87r46anab5.fsf@yun.yagibdah.de> <87vbvleiey.fsf@yun.yagibdah.de> <87vbvlbm8p.fsf@web.de> <87siqpsdgs.fsf@yun.yagibdah.de> <87iorljkhx.fsf@web.de> <87pplsivy7.fsf@yun.yagibdah.de> <87eh27mhyw.fsf@yun.yagibdah.de> <877g7yizsf.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1394918187 26071 80.91.229.3 (15 Mar 2014 21:16:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 15 Mar 2014 21:16:27 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Mar 15 22:16:35 2014 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WOvwY-0005Oi-FC for geh-help-gnu-emacs@m.gmane.org; Sat, 15 Mar 2014 22:16:34 +0100 Original-Received: from localhost ([::1]:51221 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WOvwY-0001n4-17 for geh-help-gnu-emacs@m.gmane.org; Sat, 15 Mar 2014 17:16:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41108) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WOvun-0006JQ-Ro for help-gnu-emacs@gnu.org; Sat, 15 Mar 2014 17:14:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WOvue-0002lt-7X for help-gnu-emacs@gnu.org; Sat, 15 Mar 2014 17:14:45 -0400 Original-Received: from client-194-42-186-216.muenet.net ([194.42.186.216]:36522 helo=yun.yagibdah.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WOvud-0002jZ-N3 for help-gnu-emacs@gnu.org; Sat, 15 Mar 2014 17:14:36 -0400 Original-Received: from lee by yun.yagibdah.de with local (Exim 4.80.1) (envelope-from ) id 1WOvuT-0005k8-OQ for help-gnu-emacs@gnu.org; Sat, 15 Mar 2014 22:14:25 +0100 In-Reply-To: <877g7yizsf.fsf@gmail.com> (Jambunathan K.'s message of "Thu, 13 Mar 2014 08:13:28 +0530") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Mail-Followup-To: help-gnu-emacs@gnu.org X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 194.42.186.216 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:96525 Archived-At: Jambunathan K writes: > lee writes: > >>> Another good approach is to take hi-lock.el, modify it (as little as >>> possible) to provide the feature you want, and then to submit the patch >>> for inclusion in a future Emacs. >> >> I=C2=B4d love to do that, and I think it could be done. I=C2=B4d mostly= have to >> add some things to it and probably wouldn=C2=B4t need to modify what=C2= =B4s >> already there. >> >> How would I do that? hi-lock.el is part of emacs, which is in a bzr >> repo from which I update every now and then. I could take the current >> version of hi-lock.el and put it into a git repo to work on it. In the >> meantime, the original version may change. Then what? > > 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. --=20 Knowledge is volatile and fluid. Software is power.