From: Mark Wielaard <mark@klomp.org>
To: Federico Mena Quintero <federico@gnome.org>,
jseward@acm.org, bzip2-devel@sourceware.org
Subject: Re: bzip2 1.0.7 released
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <e7df011fba1876eda07984e429c9e3e106d62f30.camel@klomp.org> (raw)
In-Reply-To: <8a040b2dc65c66c49a16f1bc698b893288cfa927.camel@gnome.org>
On Fri, 2019-06-28 at 11:04 -0500, Federico Mena Quintero wrote:
> On Fri, 2019-06-28 at 13:27 +0200, Mark Wielaard wrote:
> >
> > The patch was correct, but I misspelled Julian's last name in the
> > commit message... embarrassing. Sorry. Fixed in the attached.
>
> I have to be out today running errands, but this is great
> work! Thanks
> Julian for the insight to just split the limits in two constants and
> Mark for implementing it.
>
> Mark, do you want to do something like release a 1.0.8pre test and
> advertise it to the Ubuntu people who reported problems?
I added a note to their bug tracker [*]. Pointing to the workaround
patch. Lets do some more testing during the weekend and then decide
whether to do a new release.
Cheers,
Mark
[*]
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/1834494/comments/7
next prev parent reply other threads:[~2019-06-28 16:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Mark Wielaard
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 ` Julian Seward
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Alternative nSelectors patch (Was: bzip2 1.0.7 released) Mark Wielaard
2019-01-01 0:00 ` Julian Seward
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` bzip2 1.0.7 released Mark Wielaard
2019-01-01 0:00 ` Federico Mena Quintero
2019-01-01 0:00 ` Mark Wielaard [this message]
2019-01-01 0:00 ` bzip2 test suite (Was: bzip2 1.0.7 released) Mark Wielaard
2019-01-01 0:00 ` bzip2 1.0.7 released Jeffrey Walton
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=e7df011fba1876eda07984e429c9e3e106d62f30.camel@klomp.org \
--to=mark@klomp.org \
--cc=bzip2-devel@sourceware.org \
--cc=federico@gnome.org \
--cc=jseward@acm.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).