From: cyg Simple <cygsimple@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: bzip.org
Date: Mon, 24 Sep 2018 13:17:00 -0000 [thread overview]
Message-ID: <19d11f1b-dfd7-4e82-7f72-a170af56c1da@gmail.com> (raw)
In-Reply-To: <OF0F781EF9.241BA286-ONC1258311.002D468D-C1258311.002D5A27@onevision.com>
On 9/23/2018 4:15 AM, Roland DOT Schwingel AT onevision DOT com wrote:
> Hi,
>
Please keep on the conversation on the list.
>
>> Sadly our beloved http://www.bzip.org <http://www.bzip.org/>has hit
> the bit bucket. Â Does
>> anyone know where upstream support for bzip2 went?
>
> It appears that bzip.org is just coming back (as announced on the
> valgrind list)
>
So it is, and from there we find:
```
Find the latest version on SourceForge.
Author admin
Posted on 22 September 2018
```
But I can't find it in SourceForge search engine and there is no link
pointing to the project at the bzip.org page.
--
cyg Simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-09-24 13:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 15:33 bzip.org cyg Simple
2018-09-21 16:04 ` bzip.org Marco Atzeri
2018-09-21 17:01 ` bzip.org Jeffrey Walton
2018-09-21 17:28 ` bzip.org cyg Simple
2018-09-21 21:59 ` bzip.org Henry S. Thompson
2018-09-23 4:28 ` bzip.org cyg Simple
2018-09-23 8:56 ` bzip.org Marco Atzeri
[not found] ` <OF0F781EF9.241BA286-ONC1258311.002D468D-C1258311.002D5A27@onevision.com>
2018-09-24 13:17 ` cyg Simple [this message]
2018-09-24 21:42 ` bzip.org Jeffrey Walton
2018-10-01 20:51 ` bzip.org Keith Christian
2018-10-01 23:23 ` bzip.org cyg Simple
2018-10-02 16:05 ` bzip.org Keith Christian
2018-11-05 19:17 ` bzip.org cyg Simple
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=19d11f1b-dfd7-4e82-7f72-a170af56c1da@gmail.com \
--to=cygsimple@gmail.com \
--cc=cygwin@cygwin.com \
/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).