From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2 1/4] lighttpd: Ugprade from 1.4.39 to 1.4.45
Date: Mon, 28 Aug 2017 11:34:23 +0200 [thread overview]
Message-ID: <20170828093423.r4trzhbreiy7q2f3@pengutronix.de> (raw)
In-Reply-To: <20170826154611.wrwwcwde6tyjniu7@falbala.home.lespocky.de>
On Sat, Aug 26, 2017 at 05:46:12PM +0200, Alexander Dahl wrote:
> On Fri, Aug 25, 2017 at 10:05:13AM +0200, Alexander Dahl wrote:
> > Marking LIGHTTPD_MEMCACHE(D) as broken would be the easiest for now I
> > guess. Should this go into a separate patch, together with this one
> > upgrading from 1.4.39 to 1.4.45, or in the second one which renames the
> > lighttpd package option?
>
> Currently I prefer putting it into the second patch, together with the
> renaming of the option. I'll test that in week 35, and – if no one
> objects – send a v3 then.
Sounds good. Don't forget to change the dependency.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-08-28 9:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 10:36 [ptxdist] [PATCH v2 0/4] lighttpd: Update and suggestions from last year Alexander Dahl
2017-08-23 10:36 ` [ptxdist] [PATCH v2 1/4] lighttpd: Ugprade from 1.4.39 to 1.4.45 Alexander Dahl
2017-08-25 7:38 ` Michael Olbrich
2017-08-25 8:05 ` Alexander Dahl
2017-08-26 15:46 ` Alexander Dahl
2017-08-28 9:34 ` Michael Olbrich [this message]
2017-08-23 10:36 ` [ptxdist] [PATCH v2 2/4] lighttpd: Rename memcache option to memcached Alexander Dahl
2017-08-23 10:36 ` [ptxdist] [PATCH v2 3/4] lighttpd: Simplify additional config include Alexander Dahl
2017-08-23 10:36 ` [ptxdist] [PATCH v2 4/4] lighttpd: Install mime.conf and remove hardcoded values Alexander Dahl
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=20170828093423.r4trzhbreiy7q2f3@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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