From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: dalanicolai Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] add epub support to doc-view Date: Tue, 11 Jan 2022 11:09:33 +0100 Message-ID: References: <87y23nm28v.fsf@yahoo.com> <87k0f6619l.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000005b52405d54ba745" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30825"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Po Lu , Emacs Devel To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jan 11 11:12:04 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n7E8J-0007sM-Tj for ged-emacs-devel@m.gmane-mx.org; Tue, 11 Jan 2022 11:12:03 +0100 Original-Received: from localhost ([::1]:42266 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n7E8I-0005en-EP for ged-emacs-devel@m.gmane-mx.org; Tue, 11 Jan 2022 05:12:02 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:38008) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n7E67-0003a1-L1 for emacs-devel@gnu.org; Tue, 11 Jan 2022 05:09:47 -0500 Original-Received: from [2607:f8b0:4864:20::936] (port=34449 helo=mail-ua1-x936.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n7E65-0001IT-SI for emacs-devel@gnu.org; Tue, 11 Jan 2022 05:09:47 -0500 Original-Received: by mail-ua1-x936.google.com with SMTP id y4so28718777uad.1 for ; Tue, 11 Jan 2022 02:09:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qHx49iX56VdcA276gviWnOKEPaPDI/SrqzFXX5Sk+E4=; b=YQtr5bEZuaL0IvrZHJa+xtcLSXY/idNV1slRR2pEPO2NQE7sWjAJnYedYP0kz6HAVm 84fGPrmTKrdPSBnQPzh48zEDqiuGgldWaabsAmo49TtwhaWgkUYZWH+r+svZm3FllLYE GiVVXVOHsfQ5sfJ2a3Tx4vHPYQFyzqWDyU6S5FHWgcBjUngDnjLo+8zjBbUzySy8ijfR kSLw9f6jJTKpyyLAd3HM4VubrfujxSe03BqKt0pYMNnu4HM6kPETq3e5Ak68CgCxVb3G YP6l9hv/IoTCFk9wQ8e96Q39sdEE12syudNpDy0ocjEasTTDriTR35LL7trNCy0qpJXx FzNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qHx49iX56VdcA276gviWnOKEPaPDI/SrqzFXX5Sk+E4=; b=eaQxrKhGjksllfDhX01Mumwje5q95aU+qfKpNE1ZGYOIoFs1kWFqG2Qo92FCR50UNQ nsKfRKTz5wpcpQVoALe7HQrZmNNhpsZhvyL8iB7TpW+rRevq54pxehVDHz4V/ShfZ1L2 A/Go3MsLGm3P8GRzIJsYpmypXWZGkq7bNsvY5wn1GnQ+MGrTEWXlLQpiljDaSuUtbG+N rLyt5dIeJ98g6+kl5JX8+WiBhDQYe3fcZoJIrgNgnogamTCkGWDNNphZuBy0QXiivnTP bIs59lpS131J9XEsHEKN1cv8xLbAJAwfjIM0GwUI6mnDulL9AElz/hJOLolTFrb44BB8 iHSQ== X-Gm-Message-State: AOAM530gDNUmcO/lMIxVdxvuwNhuE2KYPhtyweOXBh+TZrmq1kNUtawC GLpefQQ4HFTnVFafc12QwdfmCKUhKsyRvos/26w= X-Google-Smtp-Source: ABdhPJxhxFf7iBA5EoYaJx7HWM8fwOKbP22SPA3BYpoeTjEqQbNTvvYLJUqcUDi+8edZ7F/Hl+vjJPGmRgNSOKBJaFY= X-Received: by 2002:a05:6102:7cc:: with SMTP id y12mr1625454vsg.29.1641895784984; Tue, 11 Jan 2022 02:09:44 -0800 (PST) In-Reply-To: <87k0f6619l.fsf@gmail.com> X-Host-Lookup-Failed: Reverse DNS lookup failed for 2607:f8b0:4864:20::936 (failed) Received-SPF: pass client-ip=2607:f8b0:4864:20::936; envelope-from=dalanicolai@gmail.com; helo=mail-ua1-x936.google.com X-Spam_score_int: -12 X-Spam_score: -1.3 X-Spam_bar: - X-Spam_report: (-1.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:284588 Archived-At: --00000000000005b52405d54ba745 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable That sounds like even I understand how to do it! Thanks, will give it a try... On Tue, 11 Jan 2022 at 10:59, Robert Pluim wrote: > >>>>> 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 ea= ch > >> 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=CA=BCre 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=CA=BCre > committing. You then just need to write a one-line summary of the > change, and describe the changes in the individual files. > > Robert > -- > --00000000000005b52405d54ba745 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
That sounds like even I understand how to do it! Thanks, w= ill give it a try...

On Tue, 11 Jan 2022 at 10:59, Robert Pluim <rpluim@gmail.com> wrote:
>>>>> On Tue= , 11 Jan 2022 10:34:01 +0100, dalanicolai <dalanicolai@gmail.com> said:

=C2=A0 =C2=A0 >>
=C2=A0 =C2=A0 >> Basically, the VCS will ask you to type in a message= describing each
=C2=A0 =C2=A0 >> commit you make.=C2=A0 You simply have to format tha= t message like you would
=C2=A0 =C2=A0 >> an entry in a ChangeLog.


=C2=A0 =C2=A0 dalanicolai> I guess you mean that git will ask to enter a= commit message? So I did that,
=C2=A0 =C2=A0 dalanicolai> but how does it get into the patch? (I am usi= ng magit, maybe I should check
=C2=A0 =C2=A0 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=CA=BCre 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=CA=BCre
committing. You then just need to write a one-line summary of the
change, and describe the changes in the individual files.

Robert
--
--00000000000005b52405d54ba745--