From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: "54066@debbugs.gnu.org" <54066@debbugs.gnu.org>
Subject: [bug#54066] [PATCH]: Update mesa to 21.3.6 (fixup release)
Date: Thu, 03 Mar 2022 16:05:47 +0000 [thread overview]
Message-ID: <OmlIu8OdIHWaHXmHRQUkfF6yqoCzM6Oh0MIdP7qVulR5fxyXEAmxBsBULWnpoH2Eo6K2NvE27tLwlNblAyIZNLCrm71ql-wv2rvstC3B5hc=@protonmail.com> (raw)
In-Reply-To: <dfENhMSf1Jajrzf40vo-nH7ODFm0I5CrywInxHILoKn8hmxbAEAbSRiOs6jdHcncPirtScdbZktWJoyJxdLiSYzshYSK6CpbGAQSEeZ2nak=@protonmail.com>
------- Original Message -------
On Tuesday, February 22nd, 2022 at 2:50 PM, John Kehayias wrote:
...
> It would be great to leverage that CI to move quickly on updates like mesa which won't (we'll check!) be introducing breaking changes, merely lots of rebuilds. Likewise with grafts->updates, though I'm less familiar with what to look out for there. I suppose this is sort of the staging branch idea, but maybe a smaller scale and quicker. Mesa, for instance, would likely have a new version(s) if this is stretched over a month or two.
>
Indeed, just after this message Mesa released 21.3.7.
Any support for a quick staging type branch to build changes, check for any major build failures, and then push to master with the substitutes?
next prev parent reply other threads:[~2022-03-03 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 16:45 [bug#54066] [PATCH]: Update mesa to 21.3.6 (fixup release) Ekaitz Zarraga
2022-02-22 19:50 ` John Kehayias via Guix-patches via
2022-03-03 16:05 ` John Kehayias via Guix-patches via [this message]
2022-05-15 14:03 ` bug#54066: " Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='OmlIu8OdIHWaHXmHRQUkfF6yqoCzM6Oh0MIdP7qVulR5fxyXEAmxBsBULWnpoH2Eo6K2NvE27tLwlNblAyIZNLCrm71ql-wv2rvstC3B5hc=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=54066@debbugs.gnu.org \
--cc=john.kehayias@protonmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.