From: foopub <foopub@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Error with do_patch when patch already applied
Date: Fri, 05 Nov 2021 16:52:25 +0100 [thread overview]
Message-ID: <20211105155225.UEZjtqCIL7HXMlytL9AUFJ-HVys0_bqY8pG0lr6-UZk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33915@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
New comment by foopub on void-packages repository
https://github.com/void-linux/void-packages/issues/33915#issuecomment-962009698
Comment:
Actually it doesn't seem like the patch has been merged upstream... I'm not good with Mercurial so I barely understand their repo structure, but unless I'm wrong this is the file in question of the `fix-i686-ppc-musl.patch`:
https://hg.mozilla.org/mozilla-central/file/f72751662b4af9b7fafa26fa9efa6a36b11b12a5/mozglue/misc/StackWalk.cpp
It's just that there's some more code added before... so the patch itself needs to be changed.
next prev parent reply other threads:[~2021-11-05 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 15:31 [ISSUE] " foopub
2021-11-05 15:43 ` foopub
2021-11-05 15:52 ` foopub [this message]
2021-11-05 16:13 ` foopub
2021-11-05 17:49 ` [ISSUE] [CLOSED] " q66
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=20211105155225.UEZjtqCIL7HXMlytL9AUFJ-HVys0_bqY8pG0lr6-UZk@z \
--to=foopub@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).