From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Maxim Cournoyer Newsgroups: gmane.emacs.bugs Subject: bug#66330: 28.2; Gnus wide reply (S W) changes Subject header when used from Debbugs thread Date: Wed, 04 Oct 2023 10:58:04 -0400 Message-ID: <877co2305f.fsf@gmail.com> References: <87v8bn6xn1.fsf@gmail.com> <83mswy6e1k.fsf@gnu.org> <87sf6qhli9.fsf@gmx.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18534"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) Cc: Eli Zaretskii , mirai@makinata.eu, 66330@debbugs.gnu.org To: Michael Albinus Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Oct 04 16:59:09 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 1qo3L9-0004YH-IM for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 04 Oct 2023 16:59:07 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qo3Kq-0006nM-SC; Wed, 04 Oct 2023 10:58:48 -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 1qo3Ko-0006gp-4k for bug-gnu-emacs@gnu.org; Wed, 04 Oct 2023 10:58:46 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qo3Kn-0005Lj-Sx for bug-gnu-emacs@gnu.org; Wed, 04 Oct 2023 10:58:45 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qo3L4-0003dI-KK for bug-gnu-emacs@gnu.org; Wed, 04 Oct 2023 10:59:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Maxim Cournoyer Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 04 Oct 2023 14:59:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 66330 X-GNU-PR-Package: emacs Original-Received: via spool by 66330-submit@debbugs.gnu.org id=B66330.169643151313928 (code B ref 66330); Wed, 04 Oct 2023 14:59:02 +0000 Original-Received: (at 66330) by debbugs.gnu.org; 4 Oct 2023 14:58:33 +0000 Original-Received: from localhost ([127.0.0.1]:45149 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qo3Ka-0003ca-LL for submit@debbugs.gnu.org; Wed, 04 Oct 2023 10:58:33 -0400 Original-Received: from mail-ua1-x934.google.com ([2607:f8b0:4864:20::934]:54566) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qo3KY-0003cK-Bf for 66330@debbugs.gnu.org; Wed, 04 Oct 2023 10:58:31 -0400 Original-Received: by mail-ua1-x934.google.com with SMTP id a1e0cc1a2514c-78f1210e27fso1116166241.1 for <66330@debbugs.gnu.org>; Wed, 04 Oct 2023 07:58:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696431486; x=1697036286; darn=debbugs.gnu.org; h=mime-version:user-agent:message-id:in-reply-to:date:references :subject:cc:to:from:from:to:cc:subject:date:message-id:reply-to; bh=V+teYlnkmF9Aj6SWMfRjhBRrflI9bwnTCpKOtIHdALU=; b=X5W6Rhs0RaCjD4x7I28YI/C1Y2P7BvgsnICtECiy70MVKx1LaCWdyk6ywueZL4o2zY +AlfQlXUQhmP6+cq450XtJqDcYhSYfVI4jJVb7wqPhWB+sTQ96ECv9aAG9w/5rOEDhCA o1q7gXdNCMNia3LI0kwaS2GJ+C7ANcbVxPxhklF9c7J9zyyf4IrjrArpiJ36OQHWY2Wy rGsVSNfauS128geEXUdwatIfOJ45SPOm6c4Ng2dqxgNgAjsBvDqhF4LM9NxNnzaVT1tu LtS/p4kuYuWHlNw89ygf1O5JCIEmMM2Y/3E94WTlqcJF5cWfjsBcdAK+QShchhRve3DN +QRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696431486; x=1697036286; h=mime-version:user-agent:message-id:in-reply-to:date:references :subject:cc:to:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=V+teYlnkmF9Aj6SWMfRjhBRrflI9bwnTCpKOtIHdALU=; b=pRIKSziRt/veGFXfzh0P/UqRfM9F8Hlr98YjIC7PJ/3uBXObBLqNG3A79+oq29E1Kf ulEeGct+ubfO0+5FwNEZhWoR4Y6X2iDRjDnSP5OK8oDv2lrgXkU0kodzaXfMa/AevIUX OK3ol16hhcXsgErnGhoHFoyU7rdhYK0GVkVxKJ3DO2cDBwgnJG4gW1K+hBQhaxNzXXdn xAdW3MH4ZNAMwbX7UPJ1XzPMM3HSRykw1xFeTdxhNHtKK0x/OADUaIVmnkg/3KjpunN+ 1fZfiHeOVy2FblD9mMY9UqTIweV0XQezyhzLb4DYgRxAVt8uwywhnfaGYdA6OZPNmo6q NB7w== X-Gm-Message-State: AOJu0YzgyY99Rc0MAMKC9XHtMdvnUVJ0JUx1QT6kHsp6CMiDIzsymTQ7 siYbC6sjkUh+Vx5fmlIOYw31ovGaLppK9g== X-Google-Smtp-Source: AGHT+IHUcceXLTUnCUMHrNfaHHwOXin0mMheo/AnW19CEbrGis0MR/xfM0Reb1At2Kfd2gickWcAPg== X-Received: by 2002:a67:b305:0:b0:452:7767:9058 with SMTP id a5-20020a67b305000000b0045277679058mr2267701vsm.31.1696431486144; Wed, 04 Oct 2023 07:58:06 -0700 (PDT) Original-Received: from hurd (dsl-141-24.b2b2c.ca. [66.158.141.24]) by smtp.gmail.com with ESMTPSA id m23-20020ae9e017000000b007740c0e52edsm1313908qkk.89.2023.10.04.07.58.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 04 Oct 2023 07:58:05 -0700 (PDT) In-Reply-To: <87sf6qhli9.fsf@gmx.de> (Michael Albinus's message of "Wed, 04 Oct 2023 09:53:02 +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:271808 Archived-At: Hello, Michael Albinus writes: > Eli Zaretskii writes: > > Hi Eli, > >>> When attempting to reply from an Emacs Debbugs thread specific email, >>> the Subject line gets set to the subject of the first email in the >>> thread rather than to that of the specific email I'm replying to, which >>> looses context. >> >> The Subject lines of emails pertaining to a discussion of a bug should >> never be changed. So I see no problem here, unless I'm missing >> something. >> >> Michael, am I wrong? > > Well, we haven't documented such a rule. But based on my experience I > would agree. There's often a message in the bug-gnu-emacs@gnu.org ML > with the subject "bug#xxxxx: Patch" or alike, which doesn't help. I'm > too old to remember all the bug numbers and their related topic, and I > read only messages in that ML with topics I'm interested in. > >>> 1. M-x debbugs-gnu-bugs 65479 >>> >>> 2. Press 'a' to load the bug despite the lack of SSL certificates. >>> >>> 3. Navigate to the message titled: >>> [bug#65479] [PATCH core-updates 02/61] gnu: Add docbook-xml-5. >>> >>> 4. Press S W to send a wide reply. >>> >>> 5. Observe that the Subject header in the email response being edited >>> has been changed to "Re: bug#65479: [PATCH core-updates 00/61] The >>> Draining of the XML & DocBook Swamp.", that is, the original subject of >>> the "bug" (its first message). >> >> This is a bad Subject line to begin with, from where I stand: it >> should not include the patch series numbers, and it should not assume >> there will be additional messages with different series numbers. >> >> The Subject lines in a bug/issue discussion should describe the >> bug/issue, not the patches sent to fix the issue. When working on bugs, I agree this behavior makes sense, where the original bug title should be kept around. I'm fine with that behavior for the 'bug-guix' tracker, which tracks bugs. Where I'd like to be able to customize/change that behavior is when working with *patches* posted to guix-patches, which is also hosted on Debbugs. These patches typically get sent via 'git send-email' and include in their subject the patch number, e.g. [PATCH v2 12/62]. I want this preserved when reviewing the patch, so that participant knows what was reviewed. > D'accord. But I guess the subject line quoted here is created by a tool > of the guix-patches toolchain. So first we shall agree about the rules > of that toolchain (I'm from Emacs, I won't dictate anything!). > > If this is an agreed behavior, we could discuss about a debbugs-gnu user > option how to handle the subject line of replies, with a different > default value for guix-patches messages. The global default shouldn't be > changed. That sounds good to me. > Well, we even have already guix specific code, see debbugs-guix.el. I > would appreciate if somebody from the guix project supports me in > writing such a patch. I'm willing to work on it. It seems you draft a plan in another reply, which I'll look at now. -- Thanks, Maxim