unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: dalanicolai <dalanicolai@gmail.com>
To: Tassilo Horn <tsdh@gnu.org>
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 11:08:17 +0100	[thread overview]
Message-ID: <CACJP=3koqNZSi6VBZrdF6XrXQtkifEnx432HotsEgPjo2bXquA@mail.gmail.com> (raw)
In-Reply-To: <CACJP=3kKT9MjmuPrvVPj_0=tiNDEH2vzxS0GdktFh0eiymUmbg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]

so I resorted to W s (Save diff as patch)

On Tue, 11 Jan 2022 at 11:04, dalanicolai <dalanicolai@gmail.com> wrote:

> Thanks, yeah I tried that, but it does not seem to work. I am selecting
> the commit first,
> but the command does not 'fill in' the range and does not create a patch
> (to me it looks like
> a bug, but probably I am doing something wrong)
>
> On Tue, 11 Jan 2022 at 10:53, Tassilo Horn <tsdh@gnu.org> wrote:
>
>> dalanicolai <dalanicolai@gmail.com> writes:
>>
>> >> 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.
>> >
>> > I guess you mean that git will ask to enter a commit message? So I did
>> > that, but how does it get into the patch? (I am using magit, maybe I
>> > should check out vc, which is what I am doing now)
>>
>> You export the commit as git patch using "git format-patch
>> <commit-or-range>".  With Magit, that's available using `W c c'.
>>
>> Bye,
>> Tassilo
>>
>

[-- Attachment #2: Type: text/html, Size: 1786 bytes --]

  reply	other threads:[~2022-01-11 10:08 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 [this message]
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='CACJP=3koqNZSi6VBZrdF6XrXQtkifEnx432HotsEgPjo2bXquA@mail.gmail.com' \
    --to=dalanicolai@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=tsdh@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).