public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: lighttpd 1.4.45-1
Date: Fri, 27 Jan 2017 20:03:00 -0000	[thread overview]
Message-ID: <201701271957.v0RJvFBj002816@int-mx10.intmail.prod.int.phx2.redhat.com> (raw)

The following packages have been uploaded to the Cygwin distribution:

* lighttpd-1.4.45-1

Security, speed, compliance, and flexibility -- all of these describe 
lighttpd which is rapidly redefining efficiency of a webserver; as it is 
designed and optimized for high performance environments. With a small 
memory footprint compared to other web-servers, effective management of the 
cpu-load, and advanced feature set, lighttpd is the perfect solution for 
every server that is suffering load problems.

This is an update to the latest upstream release:

https://www.lighttpd.net/2016/10/16/1.4.42/
https://www.lighttpd.net/2016/10/31/1.4.43/
https://www.lighttpd.net/2016/12/24/1.4.44/
https://www.lighttpd.net/2017/1/14/1.4.45/

--
Yaakov

                 reply	other threads:[~2017-01-27 20:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201701271957.v0RJvFBj002816@int-mx10.intmail.prod.int.phx2.redhat.com \
    --to=yselkowitz@cygwin.com \
    --cc=cygwin-announce@cygwin.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).