From: Leo Famulari <leo@famulari.name>
To: Stuart Dilts <stuart.dilts@gmail.com>
Cc: 34025-done@debbugs.gnu.org
Subject: bug#34025: [PATCH] Update meson to 0.49.0
Date: Wed, 9 Jan 2019 20:02:47 -0500 [thread overview]
Message-ID: <20190110010247.GA18759@jasmine.lan> (raw)
In-Reply-To: <CAOm0rWCaBWaKTr7cgJEsfcMnRJrh6KogFmj=Y+i5wKz4opSu-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
On Wed, Jan 09, 2019 at 03:50:58PM -0700, Stuart Dilts wrote:
> * gnu/packages/build-tools.scm: update the version and sha256 hash
Thank you for sending this patch!
We actually already have this change on the 'staging' branch [0], in commit
f06fdbae8d6318fdabf9c1eb686e2bfa2b9ff18a.
Updating meson will trigger a rebuild of all the packages that use the
meson-build-system.
I'm not sure how to find out exactly how many packages directly and
indirectly depend on the meson-build-system, but since the change was
pushed to the staging branch, it's probably more than 300, which is the
limit for changes on the master branch.
The manual section Submitting Patches describes the guidelines for how
many rebuilds are acceptable on the master, staging, and core-updates
branches:
https://www.gnu.org/software/guix/manual/en/html_node/Submitting-Patches.html
[0] https://git.savannah.gnu.org/cgit/guix.git/log/?h=staging
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-10 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 22:50 [bug#34025] [PATCH] Update meson to 0.49.0 Stuart Dilts
2019-01-10 1:02 ` Leo Famulari [this message]
2019-01-10 7:24 ` Efraim Flashner
2019-01-10 20:22 ` Leo Famulari
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=20190110010247.GA18759@jasmine.lan \
--to=leo@famulari.name \
--cc=34025-done@debbugs.gnu.org \
--cc=stuart.dilts@gmail.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).