unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: dalanicolai <dalanicolai@gmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: [PATCH] add epub support to doc-view
Date: Tue, 11 Jan 2022 10:32:00 +0800	[thread overview]
Message-ID: <87y23nm28v.fsf@yahoo.com> (raw)
In-Reply-To: <CACJP=3kaQyqYdwM5RiLn3+pdyvtfS78oayAaOKHTa8HEZwV+tg@mail.gmail.com> (dalanicolai@gmail.com's message of "Tue, 11 Jan 2022 03:20:19 +0100")

dalanicolai <dalanicolai@gmail.com> writes:

> I've read the info about sending patches, however, I don't understand
> the section about the changelog (it mentions that there is a changelog
> or something, but it doesn't say where).

> Also, the info tells us to write the commit log entries, but it does
> not say where to do this.

Basically, the VCS will ask you to type in a message describing each
commit you make.  You simply have to format that message like you would
an entry in a ChangeLog.

> Looking at the changelog files, I guess that info is just really
> outdated (am I right?).

The ChangeLog files are automatically generated from VCS history (your
commit log entries) every time a release is made, AFAIK.

I hope I cleared up some things.

> Anyway, the patch is in the attachment.

Thanks!  Have you signed the copyright papers?

> If there is some part of the 'protocol' that I did not understand then
> please inform me about it.

You should read CONTRIBUTE, it details the procedure quite well.



  reply	other threads:[~2022-01-11  2:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11  2:20 [PATCH] add epub support to doc-view dalanicolai
2022-01-11  2:32 ` Po Lu [this message]
2022-01-11  9:34   ` dalanicolai
2022-01-11  9:50     ` Tassilo Horn
2022-01-11 10:04       ` dalanicolai
2022-01-11 10:08         ` dalanicolai
2022-01-11 10:15         ` Robert Pluim
2022-01-11  9:59     ` Robert Pluim
2022-01-11 10:09       ` dalanicolai
2022-01-11  2:48 ` Stefan Monnier
2022-01-11  3:30   ` Stefan Kangas
2022-01-11 10:01     ` dalanicolai
2022-01-11 10:16       ` Robert Pluim
2022-01-13  9:14         ` dalanicolai
2022-01-11  9:59   ` dalanicolai
2022-01-11 10:13     ` dalanicolai
2022-01-11 14:39     ` Stefan Monnier
2022-01-13  9:25       ` dalanicolai
2022-01-14 16:15         ` dalanicolai
2022-01-14 20:02           ` dalanicolai
2022-01-26 20:28             ` dalanicolai
2022-01-27 16:05               ` Lars Ingebrigtsen
2022-01-27 21:09                 ` Iñigo Serna
2022-01-28 13:47                   ` Lars Ingebrigtsen
2022-01-28 19:51                     ` Iñigo Serna
2022-01-29 17:07                 ` dalanicolai

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=87y23nm28v.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=dalanicolai@gmail.com \
    --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).