From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] question about my pevious dhcpcd patch
Date: Thu, 14 Mar 2013 19:42:47 +0100 [thread overview]
Message-ID: <20130314194247.6ce999a5@skate> (raw)
In-Reply-To: <1363199449.8204.157.camel@genx.eng.msli.com>
Dear John Stile,
On Wed, 13 Mar 2013 11:30:49 -0700, John Stile wrote:
> First issue: I discovered I also need to copy a script directory, but
> don't see a good method to copy more than each file one at a time.
>
> Is there a good way to copy all files in dhcpcd-hooks except the
> Makefile, into $(TARGET_DIR)/libexec/dhcpcd-hooks?
>
> Right now I'm doing it one at a time like this:
> $(INSTALL) -D -m 0755 \
> $(@D)/dhcpcd-hooks/01-test \
> $(TARGET_DIR)/libexec/dhcpcd-hooks/01-test
> $(INSTALL) -D -m 0755 \
> $(@D)/dhcpcd-hooks/02-dump \
> $(TARGET_DIR)/libexec/dhcpcd-hooks/02-dump
> $(INSTALL) -D -m 0755 \
> $(@D)/dhcpcd-hooks/20-resolv.conf \
> $(TARGET_DIR)/libexec/dhcpcd-hooks/20-resolv.conf
> $(INSTALL) -D -m 0755 \
> $(@D)/dhcpcd-hooks/29-lookup-hostname \
> $(TARGET_DIR)/libexec/dhcpcd-hooks/29-lookup-hostname
> ...etc...
You should probably use $(MAKE) -C $(@D) install in order to use the
integrated installation procedure of dhcpcd Makefile.
> Second issue: how do I submit an updated patch? The first one was
> submitted a few days ago. Do i just do a fresh clone, and then try to
> add my stuff and submit via send-email, and pretend the first patch was
> never sent?
Since your patch has not yet been merged, you should resent an updated
version.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-03-14 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 18:30 [Buildroot] question about my pevious dhcpcd patch John Stile
2013-03-13 20:46 ` Arnout Vandecappelle
2013-03-14 18:42 ` Thomas Petazzoni [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=20130314194247.6ce999a5@skate \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox