From: Nick Clifton <nickc@redhat.com>
To: Indu Bhagat <indu.bhagat@oracle.com>, binutils@sourceware.org
Subject: Re: [PATCH 0/5] Reword to reflect SFrame is a stack trace format
Date: Wed, 1 Feb 2023 09:42:01 +0000 [thread overview]
Message-ID: <9b9ccbd0-f40b-606e-62ad-4b79bb20436f@redhat.com> (raw)
In-Reply-To: <20230131233429.3708328-1-indu.bhagat@oracle.com>
Hi Indu,
> This patchset amends the code comments and documentation around SFrame format
> to correctly use the term "stack trace" instead of "unwind" information. We
> had a brief dicussion on the gnu-gabi list
> https://sourceware.org/pipermail/gnu-gabi/2023q1/000521.html.
Patch set approved (in its entirety). Please apply.
Cheers
Nick
prev parent reply other threads:[~2023-02-01 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 23:34 Indu Bhagat
2023-01-31 23:34 ` [PATCH 1/5] libsframe/doc: use "stack trace" instead of "unwind" for SFrame Indu Bhagat
2023-01-31 23:34 ` [PATCH 2/5] sframe: " Indu Bhagat
2023-01-31 23:34 ` [PATCH 3/5] gas: " Indu Bhagat
2023-01-31 23:34 ` [PATCH 4/5] bfd: " Indu Bhagat
2023-01-31 23:34 ` [PATCH 5/5] ld/doc: " Indu Bhagat
2023-02-01 9:42 ` Nick Clifton [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=9b9ccbd0-f40b-606e-62ad-4b79bb20436f@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=indu.bhagat@oracle.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).