From: Robert Pluim <rpluim@gmail.com>
To: dalanicolai <dalanicolai@gmail.com>
Cc: Po Lu <luangruo@yahoo.com>, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: [PATCH] add epub support to doc-view
Date: Tue, 11 Jan 2022 10:59:50 +0100 [thread overview]
Message-ID: <87k0f6619l.fsf@gmail.com> (raw)
In-Reply-To: <CACJP=3=aOY2RUsNVrSWw_o+e+XoNw4H5rySMxkS9vwEAQft2Ww@mail.gmail.com> (dalanicolai@gmail.com's message of "Tue, 11 Jan 2022 10:34:01 +0100")
>>>>> On Tue, 11 Jan 2022 10:34:01 +0100, dalanicolai <dalanicolai@gmail.com> said:
>>
>> 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.
dalanicolai> I guess you mean that git will ask to enter a commit message? So I did that,
dalanicolai> but how does it get into the patch? (I am using magit, maybe I should check
dalanicolai> out vc, which is what I am doing now)
The commit message is part of the patch. This is git, you
should not skimp on committing locally :-) (you can always run 'git
commit --amend' if you need to make more changes to the same patch)
You then generate the patch using 'git format-patch HEAD~' or the
equivalent magit command.
Since youʼre using magit, you can start your commit, then run
`magit-generate-changelog', which will insert a skeleton ChangeLog
formatted entry based on the diffs of the files that youʼre
committing. You then just need to write a one-line summary of the
change, and describe the changes in the individual files.
Robert
--
next prev parent reply other threads:[~2022-01-11 9:59 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0f6619l.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=dalanicolai@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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.