From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] newlib: drop unused saber file
Date: Thu, 27 Jan 2022 15:49:42 +0100 [thread overview]
Message-ID: <YfKxBgGIojl+vWem@calimero.vinschen.de> (raw)
In-Reply-To: <20220127093101.18979-1-vapier@gentoo.org>
On Jan 27 04:31, Mike Frysinger wrote:
> I can't find any references to this, and it looks like a generated
> build log from a specific old sparc system.
> ---
> newlib/libc/saber | 184 ----------------------------------------------
> 1 file changed, 184 deletions(-)
> delete mode 100644 newlib/libc/saber
Ouch, yeah, please go ahead. The /limbo path is very likely not
existing on most machines anyway :)
Thanks,
Corinna
prev parent reply other threads:[~2022-01-27 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 9:31 Mike Frysinger
2022-01-27 14:49 ` 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=YfKxBgGIojl+vWem@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@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).