all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ken Manheimer <ken.manheimer@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Current documentation of current emacs patch-submission procedures?
Date: Sun, 05 Jul 2020 19:23:47 +0300	[thread overview]
Message-ID: <831rlqszfw.fsf@gnu.org> (raw)
In-Reply-To: <CAAT_zTFgk5xnRkDm4+nCJzO9PcJv4+gbTgvEnB7WL244wxPmDg@mail.gmail.com> (message from Ken Manheimer on Sun, 5 Jul 2020 12:07:47 -0400)

> From: Ken Manheimer <ken.manheimer@gmail.com>
> Date: Sun, 5 Jul 2020 12:07:47 -0400
> 
> Hi! After a long while since submitting patches (for allout.el and related stuff) I have a few new ones to
> submit, and am trying to track down canonical guidance on proper procedures for submitting them. (This
> was spurred by bug@11312, but I have some fixes for independent bugs as well.)
> 
> Traversing a maze of twisty passages (all vaguely similar) I found my way to Sending Patches, which
> describes a process that seems like what I used to do. But I'm perplexed when it comes to the part that
> mentions "commit log" with links to Change Log (and Change Log Concepts in a few ways!), seemingly
> interchangeably, particularly because the lisp/Changelog.* files in my current checkout of the git repository
> (with new commits from yesterday, for instance) have no updates since Emacs 24.3, as far as I can see.
> 
> I'm guessing that I should put the equivalent of what would have been in the ChangeLog in the commit
> messages, but thought I'd ask here for proper guidance. I welcome pointers to documents I missed that
> would have made this simpler, as well!

Yes.  Try reading CONTRIBUTE in the repository, I hope it is less
confusing.  You can also look at the style of commit log messages with
"git log".

Thanks.



  reply	other threads:[~2020-07-05 16:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-05 16:07 Current documentation of current emacs patch-submission procedures? Ken Manheimer
2020-07-05 16:23 ` Eli Zaretskii [this message]
2020-07-05 16:35   ` Ken Manheimer

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=831rlqszfw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ken.manheimer@gmail.com \
    /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.