From debbugs-submit-bounces@debbugs.gnu.org Sun Jan 01 17:09:10 2023 Received: (at 60358) by debbugs.gnu.org; 1 Jan 2023 22:09:10 +0000 Received: from localhost ([127.0.0.1]:41948 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pC6Vy-0003Gl-00 for submit@debbugs.gnu.org; Sun, 01 Jan 2023 17:09:10 -0500 Received: from planete-kraus.eu ([89.234.140.182]:44656) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pC6Vr-0003Fr-4G for 60358@debbugs.gnu.org; Sun, 01 Jan 2023 17:09:03 -0500 Received: from planete-kraus.eu (localhost.lan [127.0.0.1]) by planete-kraus.eu (OpenSMTPD) with ESMTP id ec126b8d for <60358@debbugs.gnu.org>; Sun, 1 Jan 2023 22:09:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=planete-kraus.eu; h= message-id:from:date:subject:to:mime-version; s=dkim; bh=WNOJBmk 8uC25BC4I9Egd8MIWaU8=; b=pxGMHozsGxxU4ysGodRZ2TeDqOgJ9VFNrgo/3vf UJwgAKmsB6p6r0XVhR7pQWCtX4jyWceZpZ5Z2wzez98myK+2rXg/ip2R8KcBsRXL OxewooHS6rjtX75Nx/9+OgoTgFHVnKw0woTyo7TvHYfViVM7uBexplZohlgbfG+p b6Ow= Received: by planete-kraus.eu (OpenSMTPD) with ESMTPSA id 2cc9a67c (TLSv1.3:TLS_CHACHA20_POLY1305_SHA256:256:NO) for <60358@debbugs.gnu.org>; Sun, 1 Jan 2023 22:09:01 +0000 (UTC) Message-Id: From: Vivien Kraus Date: Sun, 1 Jan 2023 22:59:29 +0100 Subject: [PATCH v11 0/4] Using a cover letter with a shallow thread style. To: 60358@debbugs.gnu.org MIME-Version: 1.0 User-Agent: Evolution 3.46.0 X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 60358 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) I tried the "deep" thread style, but unfortunately it seems that Patchwork only picked the last commit. My guess is that the email thread model that Patchwork recognizes is one cover letter, and every patch links to the cover letter. Maybe the deep thread style means that Patchwork recognizes the last commit as a new commit, looks up its parent and interprets it as the cover letter. So, maybe the penultimate patch was interpreted as the cover letter and so only the last patch made its way. I understand that you are upset because of the spam. I don’t like that either when it happens to me. I have more or less exhausted all the options that I can easily tweak in order to make the patch work with patchwork. If this doesn’t work, then I won’t try again and I will let the QA fail. That’s my last "sorry for the spam" on this issue. Sorry for the spam! Vivien Kraus (4): gnu: libunibreak: Use ucd instead of ucd-next. gnu: ucd-next: Update to 15.0.0. gnu: Add gnulib. gnu: guile-gnutls: Update to 3.7.11. gnu/packages/build-tools.scm | 202 +++++++++++++++++++++++++++++++++++ gnu/packages/tls.scm | 42 +++++--- gnu/packages/unicode.scm | 9 +- 3 files changed, 235 insertions(+), 18 deletions(-) base-commit: 6d4c53893308d7db340a2978307a214103660341 -- 2.38.1