From: Zack Weinberg <zackw@panix.com>
To: Girish Joshi <girish946@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
Girish Joshi via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] argp: argp.doc prints incorrectly when it starts with "\v" [BZ #19038]
Date: Mon, 15 Jun 2020 10:38:46 -0400 [thread overview]
Message-ID: <CAKCAbMh0nOW5AyPTyDxeC4i1NXaT-UTZgfG2m_rS0Cu-=MBcnA@mail.gmail.com> (raw)
In-Reply-To: <CALkY8p_UDAk7+XCoHmv2-XfY5VhLfycY7-McXH0JM=NzAP6FaQ@mail.gmail.com>
I wanted to review this patch, but I don't know enough about argp to
do it, and I don't have time today to learn how it works.
argp is shared with gnulib ( https://www.gnu.org/software/gnulib/ ).
I would like to suggest that you post this patch to
bug-gnulib@gnu.org. (Despite the name, this is the appropriate list
to send gnulib patches to.) There may be people reading that list who
can review your patch, and their review will be good enough for us as
well.
zw
next prev parent reply other threads:[~2020-06-15 14:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 18:13 Girish Joshi
2020-03-19 19:38 ` Girish Joshi
2020-03-21 2:03 ` DJ Delorie
2020-03-25 17:55 ` Girish Joshi
2020-05-07 19:53 ` Girish Joshi
2020-05-23 10:10 ` Girish Joshi
2020-06-14 15:50 ` Girish Joshi
2020-06-15 8:56 ` Florian Weimer
2020-06-15 9:51 ` Girish Joshi
2020-06-15 14:38 ` Zack Weinberg [this message]
2021-02-18 21:13 ` Girish Joshi
-- strict thread matches above, loose matches on Subject: below --
2019-05-06 8:55 Girish Joshi
2019-05-06 12:37 ` Florian Weimer
2019-05-06 13:38 ` Girish Joshi
2019-05-30 8:14 ` Girish Joshi
2019-05-30 12:52 ` Adhemerval Zanella
2019-07-05 9:02 ` Girish Joshi
2019-07-05 10:35 ` Girish Joshi
2019-07-25 15:33 ` Joseph Myers
2019-11-25 18:08 ` Girish Joshi
2019-11-30 14:47 ` Girish Joshi
2019-11-30 15:05 ` Carlos O'Donell
2020-01-07 17:55 ` Girish Joshi
2020-01-20 17:39 ` Girish Joshi
2020-01-24 2:59 ` Carlos O'Donell
2020-02-11 18:40 ` Girish Joshi
2020-02-20 7:09 ` Girish Joshi
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='CAKCAbMh0nOW5AyPTyDxeC4i1NXaT-UTZgfG2m_rS0Cu-=MBcnA@mail.gmail.com' \
--to=zackw@panix.com \
--cc=fweimer@redhat.com \
--cc=girish946@gmail.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).