Re: Bugs status tracking
VASUKI M <vasukim1992002@gmail.com>
From: VASUKI M <vasukim1992002@gmail.com>
To: Greg Sabino Mullane <htamfids@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
alvherre@alvh.no-ip.org
Cc: pgsql-bugs@lists.postgresql.org
Date: 2025-02-24T10:50:55Z
Lists: pgsql-bugs
Hi Greg, Thanks for the suggestion. I have now resolved those issues. You can check my repository here: GitHub Issues <https://github.com/Vasuki-git/mailing-lists/issues?q=is%3Aissue%20state%3Aopen%20sort%3Aupdated-desc> . I would appreciate it if Tom and Alvherre could review my repository. Once they approve, I will make it the main repository and work on pushing all the pgsql-bugs data there. Best, Vasuki On Sat, 22 Feb 2025 at 17:58, Greg Sabino Mullane <htamfids@gmail.com> wrote: > Looks pretty good. I would suggest getting the hyperlinks sorted out. If > you look at this bug for example: > > https://github.com/Vasuki-git/mailing-lists/issues/91 > > The message-id has an unwanted mailto link, and the first sentence has a > mangled hyperlink. > > The word wrapping seems aggressive as well; it would be nice to keep the > original formatting and allow things to be more than 80 characters (like > this sentence, which is exactly 219 characters long and has no newlines). > > Searching by partial message id is hit or miss. "CACTY" matches nothing, > but "CACTYHzjDSgV3qZu2stgBZ" does. > > That's a very well-written README.md ( > https://github.com/Vasuki-git/mailing-lists) > > > -- > Cheers, > Greg > > -- > Crunchy Data - https://www.crunchydata.com > Enterprise Postgres Software Products & Tech Support > >