From: Mathieu Othacehe <othacehe@gnu.org>
To: Greg Hogan <code@greghogan.com>
Cc: 43425@debbugs.gnu.org
Subject: [bug#43425] [PATCH] gnu: openblas: Update to 0.3.10.
Date: Fri, 18 Sep 2020 16:36:48 +0200 [thread overview]
Message-ID: <874knvywvz.fsf@gnu.org> (raw)
In-Reply-To: <CA+3U0ZnAHWLSdujBXnEyArosAm_9pLv4THjzPgTBmFxAB=UBfw@mail.gmail.com> (Greg Hogan's message of "Fri, 18 Sep 2020 10:01:40 -0400")
> 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.
We have some time frames when "staging" and "core-updates" are
open. Then, those branches are stabilized before being merged to
"master". There's no specific schedule, but usually stabilization of
those branches is advertised on the mailing list.
Right now, I think that the window is open. I rebased your openblas
patch, as well as python, llvm, boost and zstd patches on top of
core-updates. It will take me a while to build those packages, but I'll
keep you informed.
> How often is the documentation regenerated? I see the limits changed
> in the repo in June but the website has not been refreshed.
I thought it was every hour, but the mechanism may be broken.
> 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?
I always forget if a copyright addition is required for a simple
update. We should definitely add this information to the "Submitting
Patches" section.
Thanks,
Mathieu
next prev parent reply other threads:[~2020-09-18 14:37 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
2020-09-18 14:36 ` Mathieu Othacehe [this message]
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=874knvywvz.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=43425@debbugs.gnu.org \
--cc=code@greghogan.com \
/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).