All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ignacy Gawędzki" <ignacy.gawedzki@green-communications.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] nginx: Bump to version 1.15.0
Date: Fri, 29 Jun 2018 00:45:56 +0200	[thread overview]
Message-ID: <20180628224556.537guyhu7xwdkmrc@zenon.in.qult.net> (raw)
In-Reply-To: <20180628211330.66c97ec8@windsurf>

On Thu, Jun 28, 2018 at 09:13:30PM +0200, thus spake Thomas Petazzoni:
> Hello,

Hi,

> On Wed, 27 Jun 2018 15:51:46 +0200, Ignacy Gaw?dzki wrote:
> > Signed-off-by: Ignacy Gaw?dzki <ignacy.gawedzki@green-communications.fr>
> > ---
> >  ...-rework-autotest-to-be-cross-compila.patch |   6 +-
> >  ...-mechanism-allowing-to-force-feature.patch |   8 +-
> >  ...ture_run_force_result-for-each-featu.patch |  56 ++--
> >  ...auto-lib-libxslt-conf-use-pkg-config.patch |  10 +-
> >  ...ake-sys_nerr-guessing-cross-friendly.patch |  16 +-
> >  ...auto-lib-openssl-conf-use-pkg-config.patch | 249 ++++++++++++++++--
> >  ...7-auto-lib-libgd-conf-use-pkg-config.patch |   6 +-
> >  ...linux_config.h-only-include-dlfcn.h-.patch |   6 +-
> 
> What happened to those patches ? Just refreshed ?

Yes, refreshed, so that they apply properly.

> >  ...x-PCRE-condition-WRT-the-http-and-ht.patch |  33 ---
> 
> Why is this patch removed ?

It has been applied upstream.

Cheers,

Ignacy

-- 
Ignacy Gaw?dzki
R&D Engineer
Green Communications

  reply	other threads:[~2018-06-28 22:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27 13:51 [Buildroot] [PATCH 1/1] nginx: Bump to version 1.15.0 Ignacy Gawędzki
2018-06-28 19:13 ` Thomas Petazzoni
2018-06-28 22:45   ` Ignacy Gawędzki [this message]
2018-06-29  2:49 ` Baruch Siach
2018-06-29  6:39   ` Ignacy Gawędzki
2018-06-30 20:09     ` Thomas Petazzoni
2018-06-30 20:22 ` Thomas Petazzoni

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=20180628224556.537guyhu7xwdkmrc@zenon.in.qult.net \
    --to=ignacy.gawedzki@green-communications.fr \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.