From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id +AraIi++ZF8/cwAA0tVLHw (envelope-from ) for ; Fri, 18 Sep 2020 14:03:27 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id WPfIHi++ZF/qYwAA1q6Kng (envelope-from ) for ; Fri, 18 Sep 2020 14:03:27 +0000 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 D7377940539 for ; Fri, 18 Sep 2020 14:03:26 +0000 (UTC) Received: from localhost ([::1]:50482 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kJGyz-00065L-LO for larch@yhetil.org; Fri, 18 Sep 2020 10:03:25 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:55058) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kJGyc-00064z-KM for guix-patches@gnu.org; Fri, 18 Sep 2020 10:03:02 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:60546) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kJGyc-0006wR-9G for guix-patches@gnu.org; Fri, 18 Sep 2020 10:03:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kJGyc-0000Oj-3s for guix-patches@gnu.org; Fri, 18 Sep 2020 10:03:02 -0400 X-Loop: help-debbugs@gnu.org Subject: [bug#43425] [PATCH] gnu: openblas: Update to 0.3.10. Resent-From: Greg Hogan Original-Sender: "Debbugs-submit" Resent-CC: guix-patches@gnu.org Resent-Date: Fri, 18 Sep 2020 14:03:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 43425 X-GNU-PR-Package: guix-patches X-GNU-PR-Keywords: patch To: Mathieu Othacehe Cc: 43425@debbugs.gnu.org Received: via spool by 43425-submit@debbugs.gnu.org id=B43425.160043772231856 (code B ref 43425); Fri, 18 Sep 2020 14:03:02 +0000 Received: (at 43425) by debbugs.gnu.org; 18 Sep 2020 14:02:02 +0000 Received: from localhost ([127.0.0.1]:43859 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kJGxd-0008HJ-Jh for submit@debbugs.gnu.org; Fri, 18 Sep 2020 10:02:02 -0400 Received: from mail-wm1-f66.google.com ([209.85.128.66]:33896) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kJGxb-0008C6-VS for 43425@debbugs.gnu.org; Fri, 18 Sep 2020 10:02:00 -0400 Received: by mail-wm1-f66.google.com with SMTP id l15so6771652wmh.1 for <43425@debbugs.gnu.org>; Fri, 18 Sep 2020 07:01:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=greghogan-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IHBOaY6kQoeB9kuHx/iVhBZzGM2uEOJojRDtEv2nAB0=; b=VUcltKZzpwLNKWVlR2zk7/sXTIp9PGNNx7pK16kTAXPPplmUFONjdu03j7el5YPVJ2 C8fRMYnb4G5qSZNyHCsYwu1gF5oD95JPNCbFKm600xuNfShwHR5sLRL1TlN0tuCbzQNL PadAuyP24DxDP2PlPmnb7bmXcnXPzZc9AfDdc293dffdb6rDCTY4VZ/BE7D0Xm7NaPqj 7OL3BWGS3dWpEBWDE/AvQ+bsRNiIUK6UFXWQ+U94gzI6nvNmnfVmAqeiC0cc8rht/V3Y 6NN+EIrm6Vh+cVLl+r8fzqS3zVCOR5aUqOAaA8hekhkY/XooRt+fFbhWUA4EFQpH3wc1 vz4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IHBOaY6kQoeB9kuHx/iVhBZzGM2uEOJojRDtEv2nAB0=; b=Cvdy8/Zz/nEPjMa4/ExSSFOgP3wq/azUvZOxJqDFo5Kp7f+uLhVVexcN5rlDOio0/E KsUgtRgefhTKoVKIMAh5X9FsNQCFl3OlTG2U1KCbj3qucLOaw7qofZd4k2ED7crSMVAQ PH4vDTES75U9eJG7gFu7OhoJ2Lw4fHSrj2j5w8PgpIxuWfwaPp0104LMM/h3tIpE/g7+ +6mP6aubBq8Ovn/U2TMqWQRpXJSimVmTAQv04dJPFC+0WR6RMRiPd2nlJGbECyxqyDL0 e8Vx+kp+V2HTHQbCvT5Ga6i9+sRK78FXmMQYMqYz/mYT7NNqbWuvXOjtOjjyK1wQB4fb qMpw== X-Gm-Message-State: AOAM530+Ohm8vHUSui/BAD4dOiBceijWMiq6v8Fn0BeMasJgkPINt6bf R7agXUguU8oYAjJtuwRMH8zI+Co1jw6sRD9xwyabV4QZ3q/dL2Z7 X-Google-Smtp-Source: ABdhPJwTrqrX/FijyIfTGGzIvaBqJmF29v5L7bItKWpY9EjHHzEJINUY4IDqCImdtF/RAGTi6IqXt5U9mISJQWvHSXc= X-Received: by 2002:a1c:4b17:: with SMTP id y23mr13064861wma.162.1600437714027; Fri, 18 Sep 2020 07:01:54 -0700 (PDT) MIME-Version: 1.0 References: <87k0ws7bey.fsf@gnu.org> <87zh5n1rxo.fsf@gnu.org> <87sgbfz3n7.fsf@gnu.org> In-Reply-To: <87sgbfz3n7.fsf@gnu.org> From: Greg Hogan Date: Fri, 18 Sep 2020 10:01:40 -0400 Message-ID: Content-Type: multipart/alternative; boundary="0000000000006e201b05af96f154" X-Spam-Score: 0.0 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-Spam-Score: -1.0 (-) X-BeenThere: guix-patches@gnu.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+larch=yhetil.org@gnu.org Sender: "Guix-patches" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=fail (rsa verify failed) header.d=greghogan-com.20150623.gappssmtp.com header.s=20150623 header.b=VUcltKZz; dmarc=none; spf=pass (aspmx1.migadu.com: domain of guix-patches-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-patches-bounces@gnu.org X-Spam-Score: -0.01 X-TUID: 1OTqVJ+HTkAr --0000000000006e201b05af96f154 Content-Type: text/plain; charset="UTF-8" Mathieu, I was aware of the dependent-count triage but not fully understanding this process. When are commits made to staging (last commit was the merge 13 days ago) and/or core-updates (one commit since merge 4 days ago)? I see you were able to revert this commit to quiet the rebuilds, does this patch now go into core-updates or is it queued somewhere else? Is there a preferred time window for submitting highly-dependent revisions? I'm not seeing 'staging' or 'core-updates' annotations among the git logs. How often is the documentation regenerated? I see the limits changed in the repo in June but the website has not been refreshed. Is there a threshold for marking oneself in the copyright header? Such as, a simple version and checksum revision is not copyrightable but further changes must be marked? Greg On Fri, Sep 18, 2020 at 8:11 AM Mathieu Othacehe wrote: > > > Thanks for the updated version. Yes I guess it can happen but it's less > > likely. I added your copyright and edited a bit the commit message > > before applying. > > Turns out this patch causes 1912 package rebuilds. This is too much to > go to "master" branch. > > This patch, as well as other patches you sent, such as the python > update, shall instead target "core-updates" branch as explained here: > https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html. > > When it's the case do not hesitate to explicitly add "core-updates" to > the patch title so that committers forgetting to run `guix refresh -l > package`, such as myself do not choose the wrong branch :). > > Thanks, > > Mathieu > --0000000000006e201b05af96f154 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Mathieu,

I was aware of the = dependent-count triage but not fully understanding this process. When are c= ommits made to staging (last commit was the merge 13 days ago) and/or core-= updates (one commit since merge 4 days ago)? I see you were able to revert = this commit to quiet the rebuilds, does this patch now go into core-updates= or is it queued somewhere else? Is there a preferred time window for submi= tting highly-dependent revisions? I'm not seeing 'staging' or &= #39;core-updates' annotations among the git logs.

How often is the documentation regenerated? I see the limits change= d in the repo in June but the website has not been refreshed.

Is there a threshold for marking oneself in the copyright h= eader? Such as, a simple version and checksum revision is not copyrightable= but further changes must be marked?

Greg

On Fri, Sep 18, 2020 at 8:11 AM Mathieu Othacehe <othacehe@gnu.org> wr= ote:

> Thanks for the updated version. Yes I guess it can happen but it's= less
> likely. I added your copyright and edited a bit the commit message
> before applying.

Turns out this patch causes 1912 package rebuilds. This is too much to
go to "master" branch.

This patch, as well as other patches you sent, such as the python
update, shall instead target "core-updates" branch as explained h= ere:
https://guix.gnu.org/manual/en/html_= node/Submitting-Patches.html.

When it's the case do not hesitate to explicitly add "core-updates= " to
the patch title so that committers forgetting to run `guix refresh -l
package`, such as myself do not choose the wrong branch :).

Thanks,

Mathieu
--0000000000006e201b05af96f154--