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 10:34:01 +0100 Message-ID: References: <87y23nm28v.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000f594cf05d54b2764" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5878"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Emacs Devel To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jan 11 10:35:01 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 1n7DYT-0001PP-Nk for ged-emacs-devel@m.gmane-mx.org; Tue, 11 Jan 2022 10:35:01 +0100 Original-Received: from localhost ([::1]:59190 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n7DYS-0000Ob-6d for ged-emacs-devel@m.gmane-mx.org; Tue, 11 Jan 2022 04:35:00 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:56874) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n7DXj-00082F-NB for emacs-devel@gnu.org; Tue, 11 Jan 2022 04:34:15 -0500 Original-Received: from [2607:f8b0:4864:20::929] (port=41478 helo=mail-ua1-x929.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n7DXi-0003eM-4e for emacs-devel@gnu.org; Tue, 11 Jan 2022 04:34:15 -0500 Original-Received: by mail-ua1-x929.google.com with SMTP id p37so28511841uae.8 for ; Tue, 11 Jan 2022 01:34:13 -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=AhhFVVi6Lg64z6QvkZcgoqRLxvcbweTxpMwzM6VgNPs=; b=Y4lMy7vRSXS9WMeygJ045u8SjYvQr1u5XfITsImlgDy+fRDkavuxudpqRs+IfJss0r zkbsG5ueUFYI66quzjSyv7epDlUyOemx825sCZwT7DZ90pUs8fq+1u3gYxO31onMTPW4 GoUW4R8+0k+aokYxjUSUP5LHGdNI0TZYBdYz7fN0bOW1LqqN3c2CEQP9Z+2TEt+9Ghp1 mTYP4jL2m/FwYws41+t9Dia56VA0Uiri/bSfj0dKpOqaldcX5AfKNd5X2SwMBj8Zv86C hUyv7P7HThUOal2jyJcatVz/Cy+QVqT38covwe0tTWCL4leSbPK5UKUIeo+teuEVZheG f8Jg== 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=AhhFVVi6Lg64z6QvkZcgoqRLxvcbweTxpMwzM6VgNPs=; b=X6Dy1mkgFHIo5Ztpljw7ZFw/bet6ovLgrbZWV1sCM9fZWMiHxdUgTKF1IaYk9ommsv zXuWuCLSymNt3B31VMBsq0ViYaI58/U8KRgn+rPnSZkZYxM+bfGMUAdHgoBFzZ8rC6nj 0oE6vM5/3Dfl+Jmq3M1ra0k8CZkJTvy/M0lqYHtHCl2X1xMxFw5GGsJWrHWvJDzasQuf nmR7MlCYZ5o3h6obbeuuHnpaUbOijf78GEocWx59hp4Cs06Xiu1IJ7sr+DXy4QWRH37G iwVoLx1TYmtCiJpIqTuj0lWmKjDd4rXDNt8vijpihC8fsqcz/vqZfrZ0Oj5NFEec7xn4 7r/g== X-Gm-Message-State: AOAM531ayQ1T8S9goZkMJn6tTXkZWvRAg4aFq88LC/movGoMTl8waU+P LAse/sRsCwIcyeJcyKptPM5wQ5RCRae6NEXvfmY= X-Google-Smtp-Source: ABdhPJzZz2k7AqeAyv790BVyzjeWhHV/6y1I66kP86ysK0O7Ew4oFp4OJwrVzb5j+/hSvi5n3c+raWbrOSFryKVFzIc= X-Received: by 2002:ab0:6848:: with SMTP id a8mr1548997uas.137.1641893653221; Tue, 11 Jan 2022 01:34:13 -0800 (PST) In-Reply-To: <87y23nm28v.fsf@yahoo.com> X-Host-Lookup-Failed: Reverse DNS lookup failed for 2607:f8b0:4864:20::929 (failed) Received-SPF: pass client-ip=2607:f8b0:4864:20::929; envelope-from=dalanicolai@gmail.com; helo=mail-ua1-x929.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:284580 Archived-At: --000000000000f594cf05d54b2764 Content-Type: text/plain; charset="UTF-8" > > 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) The ChangeLog files are automatically generated from VCS history (your > commit log entries) every time a release is made, AFAIK. > Indeed, I think I've read that somewhere . Thanks! Have you signed the copyright papers? > yes You should read CONTRIBUTE, it details the procedure quite well. > good idea, I forgot about that document On Tue, 11 Jan 2022 at 03:32, Po Lu wrote: > dalanicolai 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. > --000000000000f594cf05d54b2764 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Basicall= y, the VCS will ask you to type in a message describing each
commit you make.=C2=A0 You simply have to format that message like you woul= d
an entry in a ChangeLog.
=C2=A0
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)

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

Indeed, I think I've read that s= omewhere .

Thanks!=C2=A0 Have you signed the copyright papers?

yes

You should read CONTRIBUTE, it details the pr= ocedure quite well.
=C2=A0
good idea, I fo= rgot about that document

On Tue, 11 Jan 2022 at 03:32, Po Lu <<= a href=3D"mailto:luangruo@yahoo.com">luangruo@yahoo.com> wrote:
<= /div>
dalanicolai <dalanicolai@gmail.co= m> writes:

> I've read the info about sending patches, however, I don't und= erstand
> 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.=C2=A0 You simply have to format that message like you woul= d
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!=C2=A0 Have you signed the copyright papers?

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

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