From: Jeff Law <jeffreyalaw@gmail.com>
To: newlib@sourceware.org
Subject: Re: Avoid using common symbols in v850 libgloss
Date: Sat, 19 Mar 2022 17:57:21 -0600 [thread overview]
Message-ID: <dcb0454e-8c51-1da3-1c84-751765cf3eef@gmail.com> (raw)
In-Reply-To: <76307cc8-a76a-fcc4-0701-ffaba067f604@SystematicSw.ab.ca>
On 3/19/2022 4:54 PM, Brian Inglis wrote:
> On 2022-03-19 13:31, Jeff Law wrote:
>> On 2022-02-10 08:03, Corinna Vinschen wrote:
>>> On Feb 9 18:58, Jeff Law wrote:
>>>> I've had this lying around for probably a year or two at this
>>>> point. It just changes all the instance of "errno" from a common
>>>> symbol to an extern.
>>>> I can't offhand recall where the actual definition is, but it
>>>> certainly exists in the generic code.
>>>> OK for the trunk?
>
>>> Yes, sure, but a real git patch would still be nice :)
> ^^^^^^^^^
> > Ping for:
> > https://sourceware.org/pipermail/newlib/2022/019155.html
>
> Maintainers expect `git format-patch` output against latest tree sent
> using `git send-email` that can be applied from mailbox/maildir by
> running `git am [--interactive] ...`.
I must have missed Corinna's response. It's been a busy few months. I
can certainly provide a git-format-patch variant in the future, assuming
I remember. I don't do much actual work on newlib these days :-)
THanks,
jeff
next prev parent reply other threads:[~2022-03-19 23:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 1:58 Jeff Law
2022-02-10 15:03 ` Corinna Vinschen
2022-03-19 22:54 ` Brian Inglis
2022-03-19 23:57 ` Jeff Law [this message]
2022-03-20 1:20 ` Mike Frysinger
2022-03-20 5:07 ` Jeff Law
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=dcb0454e-8c51-1da3-1c84-751765cf3eef@gmail.com \
--to=jeffreyalaw@gmail.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).