From: Girish Joshi <girish946@gmail.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] manual: scripts/documented.sh updated
Date: Thu, 11 Apr 2024 00:05:49 +0530 [thread overview]
Message-ID: <CALkY8p9RTyvppUeV7YcTugxjfHA7wdg0MdFpTSwgoN347NchHg@mail.gmail.com> (raw)
In-Reply-To: <d9cd97cf-8c53-4c0d-835c-e6eec97ecbd9@linaro.org>
ping.
Girish Joshi
girishjoshi.io
On Wed, Apr 3, 2024 at 10:41 PM Adhemerval Zanella Netto
<adhemerval.zanella@linaro.org> wrote:
>
>
>
> On 03/04/24 12:44, Girish Joshi wrote:
> > Hello,
> > Could someone please review this patch?
> >
> > Thanks!
> > Girish Joshi
> > girishjoshi.io
> >
> > On Tue, Apr 2, 2024 at 9:31 AM Girish Joshi <girish946@gmail.com> wrote:
> >>
> >> On Mon, Apr 1, 2024 at 10:03 PM Joe Talbott <joetalbott@gmail.com> wrote:
> >>>
> >>> I guess that information is useful. I'm attaching a patch that
> >>> reverts to 'cut -b 12' and does the grep and diff with a copy of
> >>> AVAILABLE that does not have the offsets and waits until it builds the
> >>> HTML table to get the matching line with the offset.
> >>
> >> Thanks Joe,
> >> I Just realized that this patch is archived on the patchwork. So the
> >> latest changes are not reflected there.
> >>
> >> Girish Joshi
> >> girishjoshi.io
>
> I will take a look.
next prev parent reply other threads:[~2024-04-10 18:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 14:34 Girish Joshi
2023-02-27 17:56 ` Florian Weimer
2023-03-05 6:14 ` Girish Joshi
2023-03-05 6:55 ` Girish Joshi
2023-03-11 14:48 ` Joe Simmons-Talbott
2024-03-30 18:54 ` Girish Joshi
2024-04-01 16:33 ` Joe Talbott
2024-04-02 4:01 ` Girish Joshi
2024-04-03 15:44 ` Girish Joshi
2024-04-03 17:10 ` Adhemerval Zanella Netto
2024-04-04 13:58 ` Girish Joshi
2024-04-07 8:13 ` Girish Joshi
2024-04-10 18:35 ` Girish Joshi [this message]
2024-04-11 17:18 ` Adhemerval Zanella Netto
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=CALkY8p9RTyvppUeV7YcTugxjfHA7wdg0MdFpTSwgoN347NchHg@mail.gmail.com \
--to=girish946@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@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).