From: Girish Joshi <girish946@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Girish Joshi via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] manual: scripts/documented.sh updated
Date: Sun, 5 Mar 2023 12:25:29 +0530 [thread overview]
Message-ID: <CALkY8p95ey24tg6txCNmPTx34RVd3D3Jp9DGy9SmxDRmFJUahA@mail.gmail.com> (raw)
In-Reply-To: <CALkY8p9C95pD3PpUFKkjbNfQFmFdfgxaJ2NBGrkw6vvNkhtCGA@mail.gmail.com>
Also,
> On Mon, Feb 27, 2023 at 11:26 PM Florian Weimer <fweimer@redhat.com> wrote:
> _IO_vfscanf should be recognized as an alias of vfscanf, but this is
> more of an RFE than a bug fix.
I'll try to figure out a way to mark such functions as aliases, as of
now the script does not do that.
Thanks,
Girish Joshi
On Sun, Mar 5, 2023 at 11:44 AM Girish Joshi <girish946@gmail.com> wrote:
>
> Hi Florian,
> Thanks for the review.
> Turns out `diff` was not working with the given input files, this
> patch fixes that.
> I'm not sure if there is a list of people who volunteered to document
> some specific functions.
> So that comment from the output html is removed.
>
> Thanks!
> Girish Joshi
>
> >
> > * Girish Joshi via Libc-alpha:
> >
> > > Hello,
> > > As per the Missing Functions section of master Todo list[1],
> > > scripts/documented.sh needs to be updated.
> > >
> > > Could someone please review this patch?
> > > It removes the reference to linuxthreads/*.taxi files from the script
> > > and removes the individual email address from the output.
> >
> > The script still doesn't seem to work, probably because the symbol names
> > are not extract properly:
> >
> > 43120 T _dl_mcount_wrapper 43140 T _dl_mcount_wrapper_c 43320 W clogf 43320 W clogf32
> > 435c0 T _dl_find_object 43740 T realpath 43770 T quick_exit 43790 T _IO_vfscanf
> > 437c0 T _pthread_cleanup_pus 437d0 T _pthread_cleanup_pop 437d0 W cprojf 437d0 W cprojf32
> >
> > _dl_find_object is documented.
> >
> > _IO_vfscanf should be recognized as an alias of vfscanf, but this is
> > more of an RFE than a bug fix.
> >
> > Thanks,
> > Florian
> >
next prev parent reply other threads:[~2023-03-05 6:55 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 [this message]
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
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=CALkY8p95ey24tg6txCNmPTx34RVd3D3Jp9DGy9SmxDRmFJUahA@mail.gmail.com \
--to=girish946@gmail.com \
--cc=fweimer@redhat.com \
--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).