From: "Santiago Ruano Rincón" <santiago@debian.org>
To: Mark Wielaard <mark@klomp.org>
Cc: bzip2-devel@sourceware.org,
Anibal Monsalve Salazar <anibal@debian.org>,
Anthony Fok <foka@debian.org>,
Federico Mena Quintero <federico@gnome.org>
Subject: Re: [PATCH] bzip2: Fix return value when combining --test,-t and -q.
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <20190624083116.GN6125@bartik> (raw)
In-Reply-To: <1561362056-4393-1-git-send-email-mark@klomp.org>
[-- Attachment #1: Type: text/plain, Size: 678 bytes --]
Hi,
El 24/06/19 a las 09:40, Mark Wielaard escribió:
> Hi,
>
> bzip2 lost its domain and got a new home at https://sourceware.org/bzip2/
> It also didn't see a release for a very long time. Causing various patches
> used by distros to not have been integrated upstream. We are trying to
> collect them all and do a new release.
Thanks for this.
>
> The following patch comes from Debian.
> Please let us know if we missed some others.
For information, Federico Mena (in CC) is taking over the development of
bzip2: https://people.gnome.org/~federico/blog/maintaining-bzip2.html
You should consider coordinating your efforts!
Cheers,
-- Santiago
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-06-24 8:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Mark Wielaard
2019-01-01 0:00 ` Santiago Ruano Rincón [this message]
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Releasing bzip2 1.0.7 and 1.1.0 ? Was: " Mark Wielaard
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Federico Mena Quintero
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Federico Mena Quintero
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Federico Mena Quintero
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Some cherry-picks (Was: [PATCH] bzip2: Fix return value when combining --test,-t and -q.) Mark Wielaard
2019-01-01 0:00 ` Federico Mena Quintero
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=20190624083116.GN6125@bartik \
--to=santiago@debian.org \
--cc=anibal@debian.org \
--cc=bzip2-devel@sourceware.org \
--cc=federico@gnome.org \
--cc=foka@debian.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).