From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Steps to Send a Patch for a New Feature? Date: Fri, 10 Jun 2022 09:35:25 +0300 Message-ID: <838rq510wi.fsf@gnu.org> References: Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33843"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: "Wamm K. D." Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jun 10 08:39:29 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nzYIq-0008eT-Jy for ged-emacs-devel@m.gmane-mx.org; Fri, 10 Jun 2022 08:39:28 +0200 Original-Received: from localhost ([::1]:59836 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nzYIp-0004lK-Eb for ged-emacs-devel@m.gmane-mx.org; Fri, 10 Jun 2022 02:39:27 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50888) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nzYEy-0002VS-FZ for emacs-devel@gnu.org; Fri, 10 Jun 2022 02:35:28 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:48414) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nzYEx-0002C5-7F; Fri, 10 Jun 2022 02:35:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=xw1bAVZrA9fNicViDwO+YywBGge3qKhwJpwivh6LflQ=; b=L1LYklwfQF54 H9pz/hmUQaz3xssYFXIBkcAkbA3c2YpDtnRE9X0ifKPfog/SHkNQfqHG/LwIepyZYXktiYU/zdlGw h3vZ6m4hThONt+pOCB499snqKQVxaDSXsQEs9UGBXOsNjQMUsfUFUpx95IHJw5WTKw+EnOWTQVmWh ChkpkhUZ/Yigt2AOQikP6pmbLpNiwKqcSvjS+mJDdMAU7BoDsw607v1S15W2EQRzdkXFwIU4lRuk7 waoSwtmQsd7J/ua3xHrSG856k01jfJ/YmHaTglhCalbxVEqphmusPHWsVGK4ZcqHI0sgwAd4Scbvx t3Yl/BWx2qFgrNbDkXSBcA==; Original-Received: from [87.69.77.57] (port=2612 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nzYEw-0007I8-Ks; Fri, 10 Jun 2022 02:35:26 -0400 In-Reply-To: (jaft.r@outlook.com) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:290987 Archived-At: > From: "Wamm K. D." > Date: Fri, 10 Jun 2022 00:11:39 -0500 > > 'Ello, Emacs. > > A few years ago, I was adding a feature to a library, before it was part > of Emacs proper, and ran head-first into a brick wall of executive > dysfunction. > > In the time since, the library was added to Emacs's source; I have the > bulk of the work done as the only remaining thing the author wanted was > another example of the new feature I was adding but I'm unfamiliar with > the process to send a patch for Emacs. The process is documented in CONTRIBUTE, which you will find in the top-level directory of the Emacs source tree. In a nutshell, you make the changes in your local clone of the Emacs Git repository, then send the changes as an attachment in "git format-patch" form. We prefer that you send that to bug-gnu-emacs@gnu.org, which will then be recorded by our issue tracker. TIA