From: Corinna Vinschen <vinschen@redhat.com>
To: Simon Cook <simon.cook@embecosm.com>
Cc: newlib@sourceware.org
Subject: Re: [PATCH] libgloss: riscv: Install machine/syscall.h
Date: Thu, 20 Oct 2022 16:54:11 +0200 [thread overview]
Message-ID: <Y1FhE3lDB3jRjZLf@calimero.vinschen.de> (raw)
In-Reply-To: <69aba627-698a-fcfa-bd39-8a76b4e8b188@embecosm.com>
On Oct 19 21:03, Simon Cook wrote:
> Hi Corinna,
>
> On 19/10/2022 18:14, Corinna Vinschen wrote:
> > Still, unfortunately your patch doesn't apply. It seems whitespaces,
> > especially leading TABs, are broken in your patch. I suspect your
> > MUA is breaking things. Maybe you can check this and, if all else fails,
> > just attach the patch to your mail?
>
> Sorry about that, I've attached the patch which should apply without
> whitespace errors.
That worked, pushed.
Thanks,
Corinna
prev parent reply other threads:[~2022-10-20 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 19:53 Simon Cook
2022-10-19 10:47 ` Corinna Vinschen
2022-10-19 11:04 ` Simon Cook
2022-10-19 16:14 ` Corinna Vinschen
2022-10-19 19:03 ` Simon Cook
2022-10-20 14:54 ` Corinna Vinschen [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=Y1FhE3lDB3jRjZLf@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@sourceware.org \
--cc=simon.cook@embecosm.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.
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).