mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "J. Neuschäfer" <j.neuschaefer@gmx.net>
To: musl@lists.openwall.com
Cc: "J. Neuschäfer" <j.neuschaefer@gmx.net>
Subject: Re: [musl] [PATCH MCM 0/3] musl-cross-make: add newer GCC versions
Date: Fri, 25 Oct 2024 13:39:15 +0200	[thread overview]
Message-ID: <ZxuDY6etBC6t_Y9U@probook> (raw)
In-Reply-To: <20241024133619.GX10433@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 1849 bytes --]

On Thu, Oct 24, 2024 at 09:36:20AM -0400, Rich Felker wrote:
> On Thu, Oct 24, 2024 at 09:11:42AM -0400, Rich Felker wrote:
[...]
> > Weird, I'm still getting problems. git-am gives me:
> >
> > ..git/rebase-apply/patch:40: space before tab in indent.
> >                        "|fstack-protector-strong|fstack-protector-explicit" \
> > ..git/rebase-apply/patch:88: space before tab in indent.
> >         extra_headers="s390intrin.h htmintrin.h htmxlintrin.h vecintrin.h"
> > ..git/rebase-apply/patch:89: space before tab in indent.
> >         ;;
> > ..git/rebase-apply/patch:93: space before tab in indent.
> >         cpu_type=sh
> > ..git/rebase-apply/patch:94: space before tab in indent.
> >         extra_options="${extra_options} fused-madd.opt"
> > warning: squelched 79 whitespace errors
> > warning: 84 lines add whitespace errors.

These are normal, AFAICT, and I also get them with the original patches,
which apply fine.

> > and the applied patches have context lines that should be an empty
> > line with the one-space diff prefix replaced to empty lines (no
> > leading diff space).

Ah, that's quite unfortunate

> >
> > Can you verify whether this is expected or if something is getting
> > munged in the mail?

I can confirm that this happens after the email round-trip, but not
before.

> It looks like your mailer munged them sending the attachments as
> message/rfc822 mime, which is lossy with respect to whitespace, rather
> than text/plain or something that would be safely preserved. The
> "trailing whitespace" on the context lines is missing in the actual
> message I received.

I'm sending them in a tarball now, in the hope that no mail software
looks inside.  Alternatively, you may:

git pull https://codeberg.org/neuschaefer/musl-cross-make bump


Best regards,
 jn

[-- Attachment #2: patches.tgz --]
[-- Type: application/x-gtar-compressed, Size: 16390 bytes --]

      reply	other threads:[~2024-10-25 11:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 15:40 J. Neuschäfer
2024-10-02 15:40 ` [musl] [PATCH MCM 1/3] add gcc 12.4 hash and patches J. Neuschäfer
2024-10-02 15:40 ` [musl] [PATCH MCM 2/3] add gcc 13.3 " J. Neuschäfer
2024-10-02 15:40 ` [musl] [PATCH MCM 3/3] add gcc 14.2 " J. Neuschäfer
2024-10-22 21:52 ` [musl] [PATCH MCM 0/3] musl-cross-make: add newer GCC versions Rich Felker
2024-10-23 12:29   ` J. Neuschäfer
2024-10-24 13:11     ` Rich Felker
2024-10-24 13:36       ` Rich Felker
2024-10-25 11:39         ` J. Neuschäfer [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZxuDY6etBC6t_Y9U@probook \
    --to=j.neuschaefer@gmx.net \
    --cc=musl@lists.openwall.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.vuxu.org/mirror/musl/

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).