From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH] builddeb: introduce variables for control-file customization
Date: Fri, 01 Dec 2017 15:57:45 +0000 [thread overview]
Message-ID: <1512143865.18523.126.camel@codethink.co.uk> (raw)
In-Reply-To: <20171127173037.019c138b@md1em3qc>
On Mon, 2017-11-27 at 17:30 +0100, Henning Schild wrote:
> Ben,
>
> could you please have a look at that patch. I actually need that or
> something similar to build a cip-kernel for an embedded target. But i
> thought i start off with an upstream patch and ask for a backport
> later.
I don't believe these dependencies are correct for a kernel built with
'make deb-pkg'.
I'll go and put my Debian hat on to write a longer reply.
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
prev parent reply other threads:[~2017-12-01 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171127161345.17880-1-henning.schild@siemens.com>
2017-11-27 16:30 ` [cip-dev] [PATCH] builddeb: introduce variables for control-file customization Henning Schild
2017-12-01 15:57 ` Ben Hutchings [this message]
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=1512143865.18523.126.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/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