unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Greg Hogan <code@greghogan.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 43425@debbugs.gnu.org
Subject: [bug#43425] [PATCH] gnu: openblas: Update to 0.3.10.
Date: Fri, 18 Sep 2020 10:01:40 -0400	[thread overview]
Message-ID: <CA+3U0ZnAHWLSdujBXnEyArosAm_9pLv4THjzPgTBmFxAB=UBfw@mail.gmail.com> (raw)
In-Reply-To: <87sgbfz3n7.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]

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 <othacehe@gnu.org> 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
>

[-- Attachment #2: Type: text/html, Size: 2279 bytes --]

  reply	other threads:[~2020-09-18 14:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 13:59 [bug#43425] [PATCH] gnu: openblas: Update to 0.3.10 Greg Hogan
2020-09-17 13:58 ` Mathieu Othacehe
2020-09-17 15:47   ` Greg Hogan
2020-09-18  7:10     ` bug#43425: " Mathieu Othacehe
2020-09-18 12:10       ` [bug#43425] " Mathieu Othacehe
2020-09-18 14:01         ` Greg Hogan [this message]
2020-09-18 14:36           ` Mathieu Othacehe
2020-09-25 19:02             ` Marius Bakke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+3U0ZnAHWLSdujBXnEyArosAm_9pLv4THjzPgTBmFxAB=UBfw@mail.gmail.com' \
    --to=code@greghogan.com \
    --cc=43425@debbugs.gnu.org \
    --cc=othacehe@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).