From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: Ping^4 Re: [PATCH v2] Support C2X printf %b, %B
Date: Mon, 08 Nov 2021 16:38:02 +0100 [thread overview]
Message-ID: <mwee7qk691.fsf@tomate.loria.fr> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2111081502400.2331687@digraph.polyomino.org.uk> (message from Joseph Myers on Mon, 8 Nov 2021 15:03:03 +0000)
Dear Joseph,
I tried to apply that patch to master (a6a9c1a) but it seems to fail
(conflict in NEWS):
$ git pw patch apply 46147
Applying: Support C2X printf %b, %B
Using index info to reconstruct a base tree...
M NEWS
Falling back to patching base and 3-way merge...
Auto-merging NEWS
CONFLICT (content): Merge conflict in NEWS
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Support C2X printf %b, %B
Is there any way to force the "trybot" to check again the patch with current
master?
Best regards,
Paul
> Date: Mon, 8 Nov 2021 15:03:03 +0000
> From: Joseph Myers <joseph@codesourcery.com>
> User-Agent: Alpine 2.22 (DEB 394 2020-01-19)
>
> Ping^4. Any more comments on this patch
> <https://sourceware.org/pipermail/libc-alpha/2021-October/131905.html>?
> It seems the discussion of preventing execution of binaries with an older
> glibc than that with which they were built has moved onto general
> mechanisms for doing that (if doing that ends up being considered
> desirable), rather than anything that would involve a change to this patch
> such as adding new symbol versions for 56 printf-like functions per long
> double variant.
>
> --
> Joseph S. Myers
> joseph@codesourcery.com
next prev parent reply other threads:[~2021-11-08 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 23:15 Joseph Myers
2021-10-13 0:37 ` [PATCH v2] " Joseph Myers
2021-10-18 16:05 ` Ping " Joseph Myers
2021-10-26 20:49 ` Ping^2 " Joseph Myers
2021-11-01 16:56 ` Ping^3 " Joseph Myers
2021-11-08 15:03 ` Ping^4 " Joseph Myers
2021-11-08 15:38 ` Paul Zimmermann [this message]
2021-10-20 21:00 ` H.J. Lu
2021-10-20 21:27 ` Joseph Myers
2021-11-10 9:27 ` Florian Weimer
2021-11-10 15:30 ` Joseph Myers
2021-11-10 15:37 ` Florian Weimer
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=mwee7qk691.fsf@tomate.loria.fr \
--to=paul.zimmermann@inria.fr \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).