From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#64154: 29.0.92; Provide additional details on GnuPG and EPA usage in epa.texi Date: Sun, 02 Jul 2023 15:16:04 +0300 Message-ID: <83ilb2o6ez.fsf@gnu.org> References: <83wn02r0s7.fsf@gnu.org> <90275992-b539-e611-d92b-9bfe57d9d58d@vodafonemail.de> <056aa3cb-51e6-dc01-a299-1200ba79e211@vodafonemail.de> <831qhtts01.fsf@gnu.org> <9e4c56f2-0124-fdf1-c719-ca6219c1ab28@vodafonemail.de> <3036a576-9260-8932-cb07-3941046f2dd8@vodafonemail.de> <83a5wgrwzj.fsf@gnu.org> <196f75be-0935-c481-8a9e-7157f3e650d0@vodafonemail.de> <83o7kvpn22.fsf@gnu.org> <7f41744d-bb32-1b0d-8fea-69f91b413b0c@vodafonemail.de> <83jzvjpivs.fsf@gnu.org> <5fd3e9fe-4676-99dd-0931-992f71be8728@vodafonemail.de> <83cz1aq57g.fsf@gnu.org> <77ffb12e-fca1-96bf-ce9f-4bd7d63f1763@vodafonemail.de> <83wmziohee.fsf@gnu.org> <4c623320-b950-9514-3d18-b051d136262b@vodafonemail.de> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9057"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 64154@debbugs.gnu.org To: Jens Schmidt Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Jul 02 14:16:17 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1qFw00-0002AJ-KL for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 02 Jul 2023 14:16:16 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qFvzp-0005Gu-1t; Sun, 02 Jul 2023 08:16:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qFvzn-0005ES-3y for bug-gnu-emacs@gnu.org; Sun, 02 Jul 2023 08:16:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qFvzm-0007mq-OH for bug-gnu-emacs@gnu.org; Sun, 02 Jul 2023 08:16:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qFvzm-0001ZE-Ah for bug-gnu-emacs@gnu.org; Sun, 02 Jul 2023 08:16:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 02 Jul 2023 12:16:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 64154 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 64154-submit@debbugs.gnu.org id=B64154.16883001385992 (code B ref 64154); Sun, 02 Jul 2023 12:16:02 +0000 Original-Received: (at 64154) by debbugs.gnu.org; 2 Jul 2023 12:15:38 +0000 Original-Received: from localhost ([127.0.0.1]:59467 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qFvzO-0001Ya-36 for submit@debbugs.gnu.org; Sun, 02 Jul 2023 08:15:38 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:59382) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qFvzL-0001YL-NY for 64154@debbugs.gnu.org; Sun, 02 Jul 2023 08:15:36 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qFvzG-0007Yv-2I; Sun, 02 Jul 2023 08:15:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=MzN4wS7AzR/rLEEpZBJ4eK6WLSSVE+hu0x4nHaOw4Y0=; b=HfiRpu8Lki/P 14TllkH+U3/FKMCZpA8lIqMzQeBTKyWUNfWSAHRzG9f8mon5eBfBsaFf1JhRaDXJhWDA4DfaApAYv XnGfsXen80X8oEw1Z7Kq6STmJtu02P1QYFEH8knJNnDmApA8pI1bdrzuMQBSrdKv6VoaOHQHvxlTK 7YdTTRMwiMCGOxiHptftyp06pHz52nyhg+A+7GyAeXLI2e5gmot8XRIRAXLTawJzZDNo8lyS+0yB7 atoJldzH8DeHgxtPxbkCz2BNhysLRe/S1BG4w9qIHPZ0KaOY2J+MasVXR4nWafa2noFt1c9uOVkS4 UdBMFkg8eTdsiXwj20wISQ==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qFvzF-0006QY-6T; Sun, 02 Jul 2023 08:15:29 -0400 In-Reply-To: <4c623320-b950-9514-3d18-b051d136262b@vodafonemail.de> (message from Jens Schmidt on Sun, 2 Jul 2023 13:54:16 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:264480 Archived-At: > Date: Sun, 2 Jul 2023 13:54:16 +0200 > Cc: 64154@debbugs.gnu.org > From: Jens Schmidt > > On 2023-07-02 10:18, Eli Zaretskii wrote: > > > Can you send a single patch with all the changes, please? > > Ok, next general question, probably I have misunderstood your previous > comment on that. git lingo is still somewhat new to me... > > Suppose I provide a patch P1 on emacs-29 and you review P1. How should > I provide the changes CH resulting from that review? With a patch P2 > like this (A): > > emacs-29 -> P1 -> P2 > > Or with a patch P1' merging P1 and P2 like this (B): > > emacs-29 -> P1' > > Or does it depend on the changes CH and you decide case-by-case (C)? I usually prefer to see a single patch relative to the current Git, even in subsequent reviews.