From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:403:478a::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id cOCxEQL5/mQbvgAAG6o9tA:P1 (envelope-from ) for ; Mon, 11 Sep 2023 13:24:50 +0200 Received: from aspmx1.migadu.com ([2001:41d0:403:478a::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id cOCxEQL5/mQbvgAAG6o9tA (envelope-from ) for ; Mon, 11 Sep 2023 13:24:50 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id D442E325B0 for ; Mon, 11 Sep 2023 13:24:49 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20221208 header.b=Ubfsv8f8; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1694431490; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=4uN8tIetuQKWRxzVGOy9TWqu7WFAumDmIGEjCJOuxZg=; b=YXNV9/sxo+CFuGoNGPSSiR0mjiSmvuyFxz/J2nlkgcb2gScQvGug6XPPD/hPN6wzuIchz1 5hqWDBh4LQOGf+bsj9rKoErcDbVXgorRE6bT8IswBHZJN4KSksiehJUTR1JL1thIZk7T/b h2JAtxwIpsydHcX0OfHOy2gQRxiHznWUHCVi0bmWUJKyoxyLVtuwO20RnuYJQAs41bzdLJ HmTBDGegiPpGRB/xncJzibKQqvD5060f8vhw8mNJZrB6E3YTJth14OuN+l3lQcqkEYgvdM CV5CIb43RntUpsdIFyCkWzzV43fU7YOGZoD9Gqg5Bidzw+pgdCZhL7UUzFp3Jw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1694431490; a=rsa-sha256; cv=none; b=qhvXIkfU9AF9XIN+0Ue/OPngd56Z6ojd1jSLa7FtFHdX6bDBa8SGRhG/lSAABLUViWt+jn D1ss7H26iyEx5A0KBbBMUU566wkgpwLc2XKzUtYKYPWXg0odcOEL3wvYU3emCPXRLy04EK OsS8bG2gkn1mquDRbtbUd4sTG0sFcwh+yEhHsVaGlPrIvhMT0b9dFxE6QsQJXYm/maSw2H MnMJeGA6SWAfZemHQIMn34PnLczQjRsmfCdD52dfyuCEKkh/6s8chVirW0lEKwLR0mSMwR E7o9KxmjRQYb9B2jm2NIm6OuQb2cbdJv+l19AV2AP5Obo9CZhEUawGPR8/X+ag== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20221208 header.b=Ubfsv8f8; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qff1Y-0004WB-Eu; Mon, 11 Sep 2023 07:24:12 -0400 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 1qff1X-0004UD-5N for guix-devel@gnu.org; Mon, 11 Sep 2023 07:24:11 -0400 Received: from mail-wm1-x330.google.com ([2a00:1450:4864:20::330]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qff1R-0006qc-2q for guix-devel@gnu.org; Mon, 11 Sep 2023 07:24:10 -0400 Received: by mail-wm1-x330.google.com with SMTP id 5b1f17b1804b1-401e6ce2d9fso12831645e9.1 for ; Mon, 11 Sep 2023 04:24:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694431443; x=1695036243; darn=gnu.org; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:from:to:cc:subject:date:message-id :reply-to; bh=4uN8tIetuQKWRxzVGOy9TWqu7WFAumDmIGEjCJOuxZg=; b=Ubfsv8f8ClBpmohrBrtz3gIaBO/3XiBgqc/V7XyxBHj8Oz8ivRhpqlzkRbUixQMXLz M54ydvB2XB8XCTati2893dCSvEfnUTrBdcsLCeq+uGA0+DaZFTZk3DJjju3MwWci3h0F eHr0pfIFBdJ6iV7FdU60EBIzCLRNbz1z51LW2T6vxO0etPGcuYyjJNTxAa9G3W+y86yh QU4p3zetCp5NpCE4ZQQPodkFSvEY1BsxCkKj7mmv8NUVMDe3MLeO6zSW6cInHhZb1xOu 8sBVMMIboE6GGrIl2aO9I1YpseVPQoM5g1HlS0wYksTZgvubcmkDLDO148U29oj+AdIO ULmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694431443; x=1695036243; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=4uN8tIetuQKWRxzVGOy9TWqu7WFAumDmIGEjCJOuxZg=; b=He35i01hJnAN2XOGwyXB3Jx8zcNcjq3DLzTI5FbJOY/4FNb7Qww/c8+0f6K3JxQKvC VQLR2h2yVdYtu3qR2XU3EafZAXoM52cbcOchmOmaeZu2NouT+r6I2HEXqwnfv1uC/mpk TWCIoQ6FSo8dt1ok/vX+VCRGWQVRhzcFsSRPZQcFaiKBeMwvq2nFRxr/yCHRUP85MzgS NyTwmIc8ayZioX1xtwW/ZNSI+De4i2NMHi+WO0qtYDl7FGKpnXNzo7N4ijMK0jnQyUoK VW8PH+RFCqwhXN/TSf4GZy/02Ns4mb0PlA9Xj5AJ6g1D551JJDlu4lGVb4OGxDbsvtzN RpQg== X-Gm-Message-State: AOJu0YxwWqe5Ay+PB7W6r2KwLxwVcRhZ/VyWDLxs7ic1qpDxxqqGZfi1 xEubWWwx/2FjGloSHLB4SuokLxynnJQ= X-Google-Smtp-Source: AGHT+IH49R0wZrUudjxVydraSUDWK5mF9b93CrQdbzns0neroHQ9Sy4OuszxV6gyuhV70N1b7NuqTg== X-Received: by 2002:a5d:64c6:0:b0:31f:af30:1bd4 with SMTP id f6-20020a5d64c6000000b0031faf301bd4mr1247716wri.1.1694431443307; Mon, 11 Sep 2023 04:24:03 -0700 (PDT) Received: from pfiuh07 ([193.48.40.241]) by smtp.gmail.com with ESMTPSA id r3-20020a5d4983000000b00317ab75748bsm9730417wrq.49.2023.09.11.04.24.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 11 Sep 2023 04:24:03 -0700 (PDT) From: Simon Tournier To: Maxim Cournoyer , Vagrant Cascadian Cc: Felix Lechner , Giovanni Biscuolo , guix-devel@gnu.org Subject: Re: [workflow] Automatically close bug report when a patch is committed In-Reply-To: <87ledex5xr.fsf@gmail.com> References: <8734zrn1sc.fsf@xelera.eu> <87edjb5le5.fsf@gmail.com> <86o7ien856.fsf@gmail.com> <87h6o6fdgv.fsf@xelera.eu> <877cp2nn91.fsf@gmail.com> <871qfam14v.fsf@wireframe> <87ledex5xr.fsf@gmail.com> Date: Mon, 11 Sep 2023 13:00:07 +0200 Message-ID: <87bke9j7pk.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2a00:1450:4864:20::330; envelope-from=zimon.toutoune@gmail.com; helo=mail-wm1-x330.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Scanner: mx0.migadu.com X-Migadu-Spam-Score: -1.11 X-Spam-Score: -1.11 X-Migadu-Queue-Id: D442E325B0 X-TUID: p2yFGQvj7XqH Hi Maxim, On Sat, 09 Sep 2023 at 19:50, Maxim Cournoyer w= rote: >>> --8<---------------cut here---------------start------------->8--- >>> random=3D$({ git var GIT_COMMITTER_IDENT ; echo "$refhash" ; cat "$1"; = } | >>> git hash-object --stdin) >>> --8<---------------cut here---------------end--------------->8--- >> >> That seems like it would only work if the patch was identical, as >> opposed to a slightly rebased patch on top of newer patches on master? >> >> How can you correlate Change-Id to a patch in the tracker? > > The Change-Id stays the same unless you manually edit it out of your > commit message when amending / rebasing, so the commit hash may change > while the Change-Id stays the same. So you can rebase your feature > branch on master and share a v2, whose existing commits will have the > same Change-Ids (newly added commits would get their own Change-Id > trailer). I am sorry if I am slow but I do not understand. --8<---------------cut here---------------start------------->8--- $ git var GIT_COMMITTER_IDENT Simon Tournier 1694428674 +0200 $ git var GIT_COMMITTER_IDENT Simon Tournier 1694428800 +0200 --8<---------------cut here---------------end--------------->8--- Therefore this Change-Id can be different for the same series, depending when I am locally committing. No? And sorry if I am slow but I am also missing your answer about =E2=80=9CHow= can you correlate Change-Id to a patch in the tracker?=E2=80=9D. How is this Change-Id correlated to the Debbugs number? Let take an example. :-) Assume Change-Id was used for your submission bug#65280 about Qt. It reads many patches and we have: 02/59 1717c8a233b7fda3a10aabc061168c71317f883e AuthorDate: Fri Aug 11 15:26:14 2023 -0400 59/59 0a77b869322274030c4c0e8315ddea802da44c92 AuthorDate: Tue Aug 15 16:20:10 2023 -0400 >From my understanding, 1. GIT_COMMITTER_IDENT depends on time so these two commits would have a different Change-Id, no? 2. How is Change-Id linked to #65280? Cheers, simon