From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/2] package/unscd: new package
Date: Mon, 30 Nov 2015 23:22:38 +0100 [thread overview]
Message-ID: <20151130232238.401bc727@free-electrons.com> (raw)
In-Reply-To: <565CCAEE.7070503@mind.be>
Arnout,
On Mon, 30 Nov 2015 23:17:18 +0100, Arnout Vandecappelle wrote:
> >>>> unscd 0.51 Patching
> > support/scripts/apply-patches.sh /home/thomas/projets/buildroot/output/build/unscd-0.51 /home/thomas/projets/buildroot/output/build/unscd-0.51/debian/patches
> > Unsupported file type for /home/thomas/projets/buildroot/output/build/unscd-0.51/debian/patches/change_invalidate_request_info_output, skipping
> > Unsupported file type for /home/thomas/projets/buildroot/output/build/unscd-0.51/debian/patches/support_large_numbers_in_config, skipping
>
> Uh, that shouldn't happen, since 7caf464 everything in the series file should
> be applied regardless of name...
I tested on top of next, so it should have worked... but it did not. I
didn't check if the patches were actually applied, but it is clear that
this message was displayed, since I copy/pasted from my terminal.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-30 22:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 13:58 [Buildroot] [PATCH v5 0/2] package/unscd: new package Doug Kehn
2015-11-23 13:58 ` [Buildroot] [PATCH v5 1/2] " Doug Kehn
2015-11-30 21:44 ` Thomas Petazzoni
2015-11-30 22:17 ` Arnout Vandecappelle
2015-11-30 22:22 ` Thomas Petazzoni [this message]
2015-11-30 22:24 ` Arnout Vandecappelle
2015-11-30 22:44 ` Thomas Petazzoni
2015-12-01 13:07 ` rdkehn at yahoo.com
2015-11-23 13:58 ` [Buildroot] [PATCH v5 2/2] toolchain/toolchain-common.in: install nscd Doug Kehn
2015-11-30 22:08 ` Thomas Petazzoni
2015-11-23 14:35 ` [Buildroot] [PATCH v5 0/2] package/unscd: new package Vicente Olivert Riera
2015-11-23 16:32 ` rdkehn at yahoo.com
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=20151130232238.401bc727@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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.