All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] customize: fix copy paths
Date: Wed, 5 May 2010 22:51:06 +0000 (UTC)	[thread overview]
Message-ID: <hrssoq$a34$1@dough.gmane.org> (raw)
In-Reply-To: 1273097819-8002-1-git-send-email-luca@lucaceresoli.net

On 2010-05-05, luca at lucaceresoli.net <luca@lucaceresoli.net> wrote:

> From: Luca Ceresoli <luca@lucaceresoli.net>
>
> customize.mk used to copy files with a wrong command, resulting in one
> directory level in excess. For example, source/etc/myfile would have
> produced /etc/etc/myfile in the target filesystem instead of /etc/myfile.

Yup:

  https://bugs.busybox.net/show_bug.cgi?id=849
  https://bugs.busybox.net/show_bug.cgi?id=1135

-- 
Grant Edwards               grant.b.edwards        Yow! Thank god!! ... It's
                                  at               HENNY YOUNGMAN!!
                              gmail.com            

  reply	other threads:[~2010-05-05 22:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 22:16 [Buildroot] [PATCH] customize: fix copy paths luca at lucaceresoli.net
2010-05-05 22:51 ` Grant Edwards [this message]
2010-05-06 21:29 ` Peter Korsgaard

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='hrssoq$a34$1@dough.gmane.org' \
    --to=grant.b.edwards@gmail.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.