From: Marius Bakke <marius@gnu.org>
To: Michael Rohleder <mike@rohleder.de>
Cc: 42468-done@debbugs.gnu.org
Subject: [bug#42468] [PATCH] gnu: patchelf: Update to 0.11.
Date: Sat, 25 Jul 2020 16:43:00 +0200 [thread overview]
Message-ID: <87365fwt8r.fsf@gnu.org> (raw)
In-Reply-To: <87v9ig8hgp.fsf@rohleder.de>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
Michael Rohleder <mike@rohleder.de> writes:
> Marius Bakke <marius@gnu.org> writes:
>> Uh, I did not realize patchelf had 700+ dependencies (because it is used
>> for GHC), so I reverted this on 'master' and applied it on 'staging'
>> instead.
>>
>> You can check the amount of rebuilds a package change will cause with
>> 'guix refresh -l patchelf'. It's good practice to use --subject-prefix
>> with 'PATCH staging' or 'PATCH core-updates' when emailing patches to
>> prevent overworked reviewers from breaking master on your behalf. ;-)
>>
>> Sorry for the mishap!
>>
>
> Uh, yes, sorry for your wasted time!
>
> I checked the dependencies and wanted to send to staging, but before
> sending I got distracted from realworld and then forgot the prefix in
> the subject (and was offline till now)... Sorry! I have to be more
> careful next time!
No worries, we don't really expect contributors to know about these
things. Sorry if my comment sounded angry, it was late. ;-)
You've been around a while now, consider applying for commit access so
you can break master all by yourself, by the way!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-07-25 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 17:35 [bug#42468] [PATCH] gnu: patchelf: Update to 0.11 Michael Rohleder
2020-07-21 21:30 ` bug#42468: " Marius Bakke
2020-07-21 23:44 ` [bug#42468] " Marius Bakke
2020-07-22 1:29 ` Michael Rohleder
2020-07-25 14:43 ` Marius Bakke [this message]
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=87365fwt8r.fsf@gnu.org \
--to=marius@gnu.org \
--cc=42468-done@debbugs.gnu.org \
--cc=mike@rohleder.de \
/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).