mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] updates lighttpd version 1.4.39 -> 1.4.42
Date: Fri, 21 Oct 2016 13:59:34 +0200	[thread overview]
Message-ID: <20161021115933.GA13453@archie.localdomain> (raw)
In-Reply-To: <4fe11615-44b5-1766-1529-6fe955bcb970@atsonline.de>

On Fri, Oct 21, 2016 at 12:41:48PM +0200, Andreas Geisenhainer wrote:
> On 21/10/16 11:28 AM, Michael Olbrich wrote:
> > On Fri, Oct 21, 2016 at 10:26:37AM +0200, Andreas Geisenhainer wrote:
> > > -config LIGHTTPD_MEMCACHE
> > > +config LIGHTTPD_MEMCACHED
> > This deserves entry in scripts/migrate/migrate_ptx to help migration. There
> > should be enough examples show how it works if you are unfamiliar with sed
> > scripts.
> 
> I'll look into it. Thanks for the pointer.
> Should the migration from->to be based on the current->next
> release?

Hi,

is it really necessary to change LIGHTTPD_MEMCACHE to
LIGHTTPD_MEMCACHED just because they changed the configure option to
better reflect the name of the daemon? Is it worth the hassle of
migrating it?

Thanks,
Clemens


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2016-10-21 11:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21  8:26 Andreas Geisenhainer
2016-10-21  9:28 ` Michael Olbrich
2016-10-21 10:41   ` Andreas Geisenhainer
2016-10-21 11:59     ` Clemens Gruber [this message]
2016-10-21 15:25       ` Michael Olbrich
2016-10-21 15:24     ` Michael Olbrich
2016-10-24  9:33       ` Andreas Geisenhainer
2016-10-24 11:48         ` Michael Olbrich
2016-10-24 13:21           ` Andreas Geisenhainer
2016-10-21 10:05 ` Alexander Dahl
2016-10-31 14:16   ` Alexander Dahl
2016-10-31 15:14     ` Clemens Gruber
2016-11-11  9:23       ` Michael Olbrich

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=20161021115933.GA13453@archie.localdomain \
    --to=clemens.gruber@pqgruber.com \
    --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