unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Wamm K. D." <jaft.r@outlook.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Steps to Send a Patch for a New Feature?
Date: Fri, 10 Jun 2022 01:45:32 -0500	[thread overview]
Message-ID: <BY5PR07MB7029C5E7A42637B6027CC69A99A69@BY5PR07MB7029.namprd07.prod.outlook.com> (raw)
In-Reply-To: <838rq510wi.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Jun 2022 02:35:28 -0400")

On Fri. (Jun 10, 2022) at 02:35:28 AM -04, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: "Wamm K. D." <jaft.r@outlook.com>
>> 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

Awesome; 'sounds good. Every resource I was able to find only specified
sending bugs to bug-gnu-emacs@gnu.org so I wasn't sure if new features
should be sent there, as well. Thanks so much (again) for the guidance;
'very much appreciated.



  reply	other threads:[~2022-06-10  6:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10  5:11 Steps to Send a Patch for a New Feature? Wamm K. D.
2022-06-10  6:35 ` Eli Zaretskii
2022-06-10  6:45   ` Wamm K. D. [this message]
2022-06-10  8:39     ` Philip Kaludercic
2022-06-11  6:58       ` Wamm K. D.

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=BY5PR07MB7029C5E7A42637B6027CC69A99A69@BY5PR07MB7029.namprd07.prod.outlook.com \
    --to=jaft.r@outlook.com \
    --cc=eliz@gnu.org \
    --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).