From: Helge Kreutzmann <debian@helgefjell.de>
To: Mark Wielaard <mark@klomp.org>
Cc: bzip2-devel@sourceware.org
Subject: Re: Errors in man pages of bzip2
Date: Thu, 21 Apr 2022 17:47:42 +0200 [thread overview]
Message-ID: <20220421154742.GA20813@Debian-50-lenny-64-minimal> (raw)
In-Reply-To: <YmCRfFXiA/46Hfhq@wildebeest.org>
[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]
Hello Mark,
On Thu, Apr 21, 2022 at 01:04:28AM +0200, Mark Wielaard wrote:
> On Wed, Apr 20, 2022 at 04:44:27PM +0200, Helge Kreutzmann wrote:
> > On Tue, Apr 19, 2022 at 11:36:50PM +0200, Mark Wielaard wrote:
> > > On Sat, Feb 05, 2022 at 11:35:40AM +0100, Helge Kreutzmann wrote:
> > > If you could file future issues in bugzilla:
> > > https://sourceware.org/bugzilla/enter_bug.cgi?product=bzip2
> > > Then there is an archive. But sending reports to this list is also
> > > fine.
> >
> > I can do this; however in February I was told by Micah Snyder to use
> > https://gitlab.com/groups/bzip2/-/issues
> >
> > Is the sourcware bugzilla now preferred?
>
> I guess the coordination between the projects isn't ideal. But yes,
> for stable bzip2 1.0.x, which is what distros ship, sourceware is
> preferred. The gitlab project is working on an experimental 1.1
> version and rust translation.
Thanks for the clarification. I added the sourceware bugzilla to our
configuration for bzip2. So if any translator should find something
else, I'll report it there.
Also thanks for handling the update.
Greetings
Helge
--
Dr. Helge Kreutzmann debian@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-04-21 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 10:35 Helge Kreutzmann
2022-04-19 21:36 ` Mark Wielaard
2022-04-20 14:44 ` Helge Kreutzmann
2022-04-20 23:04 ` Mark Wielaard
2022-04-21 15:47 ` Helge Kreutzmann [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=20220421154742.GA20813@Debian-50-lenny-64-minimal \
--to=debian@helgefjell.de \
--cc=bzip2-devel@sourceware.org \
--cc=mark@klomp.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).