From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Robert Pluim Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] add epub support to doc-view Date: Tue, 11 Jan 2022 10:59:50 +0100 Message-ID: <87k0f6619l.fsf@gmail.com> References: <87y23nm28v.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14182"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Po Lu , Emacs Devel To: dalanicolai Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jan 11 11:08:33 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 1n7E4v-0003ZB-2I for ged-emacs-devel@m.gmane-mx.org; Tue, 11 Jan 2022 11:08:33 +0100 Original-Received: from localhost ([::1]:37450 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n7E4t-0002Gg-V3 for ged-emacs-devel@m.gmane-mx.org; Tue, 11 Jan 2022 05:08:31 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:35794) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n7DwY-0004Ya-Vr for emacs-devel@gnu.org; Tue, 11 Jan 2022 04:59:55 -0500 Original-Received: from [2a00:1450:4864:20::331] (port=45977 helo=mail-wm1-x331.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n7DwX-0007yY-J8 for emacs-devel@gnu.org; Tue, 11 Jan 2022 04:59:54 -0500 Original-Received: by mail-wm1-x331.google.com with SMTP id c126-20020a1c9a84000000b00346f9ebee43so1456724wme.4 for ; Tue, 11 Jan 2022 01:59:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:references:gmane-reply-to-list:date:in-reply-to :message-id:mime-version:content-transfer-encoding; bh=A6OcIXg5sr6d2xOoTMXr/nln4pvqy9ZVamgRqwhKVqw=; b=nKG/T0Ts8pXbOE5wErcbMJ6niYbgq2dpWnqAfYMV/trSiq7zGbs0tTS7aiAjoKpUfY Ec7cJTHPzmDeVWewfkdHASyAhRsMjASNLKwTHpXEw5kEQnU1cjo9JvF125Tz4UfBYJ7A U0D/SwPN5rqXoybulikpr8bvSmSJ00VwIVH3pY04CtHCjqUyG2IXU9PZ84BT53jyAknV fE2tlmPKBEP7chhLh1aguceXnjvp3KuZ26ouBEMg5FnOsBNCV3I+UoflcgUafun6mZtd gawN1Mj/RKA/Ja62boyfwWSo99+quo/D4tN/GUkt+JvtHozqgjWHepHGOh2EOWiY9BgV Z/1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:references :gmane-reply-to-list:date:in-reply-to:message-id:mime-version :content-transfer-encoding; bh=A6OcIXg5sr6d2xOoTMXr/nln4pvqy9ZVamgRqwhKVqw=; b=O1WuumKSFd+k2CIxetskxAF2RMQQRkzf1vc9shIf4+Eb/0Sxqtcwtx75YE2yaniLeC BoMiKhJ1gC14hKkzA8s11rA4TrZU8kEMXwp+8B2rNvBU/pQlHaHLiRn7W68//2qQt8ys mFa6M9nl4xsyXHGm7HDsOJd+poeo03XsR3Z3RhdK3nBj0ONMJFFrxfsk7ZcodieCKe4o 0B9CSwsqcZn07OJbmR8puqZwhP267oE0QxdNlnprTnnbKCnQ6N4XKJvcIc6UwfLPewC1 G2etzPzOIAPz2Ig8J4Nt5rj8QtH8EJBJhCH/VIRv/nu33G60GgQ5OwNKNxz6uamxXTPD lvEA== X-Gm-Message-State: AOAM533rbcKgHz8320mdQtey7QFhlH7fGgvhxhk5tb4LhRK9yzA7vEs3 kIskX1ECPGXwoZ3KsgUIl60FmZC0TY0= X-Google-Smtp-Source: ABdhPJwN1yMzA+WJmolHjPmczx8WusdabQStYpH1+X5go0cZEAF9PJuG7oSDX02j5Bza/jsOmYByPg== X-Received: by 2002:a1c:a5c2:: with SMTP id o185mr1740427wme.177.1641895191276; Tue, 11 Jan 2022 01:59:51 -0800 (PST) Original-Received: from rltb ([2a01:e0a:3f3:fb50:ec7:b2b7:a166:15c0]) by smtp.gmail.com with ESMTPSA id q8sm7185502wrz.66.2022.01.11.01.59.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Jan 2022 01:59:50 -0800 (PST) Gmane-Reply-To-List: yes In-Reply-To: (dalanicolai@gmail.com's message of "Tue, 11 Jan 2022 10:34:01 +0100") X-Host-Lookup-Failed: Reverse DNS lookup failed for 2a00:1450:4864:20::331 (failed) Received-SPF: pass client-ip=2a00:1450:4864:20::331; envelope-from=rpluim@gmail.com; helo=mail-wm1-x331.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, 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:284586 Archived-At: >>>>> On Tue, 11 Jan 2022 10:34:01 +0100, dalanicolai said: >>=20 >> 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 wo= uld >> an entry in a ChangeLog. dalanicolai> I guess you mean that git will ask to enter a commit messa= ge? So I did that, dalanicolai> but how does it get into the patch? (I am using magit, may= be 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 --=20