From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] [skeleton] move default skeleton to fs/ and drop busybox skeleton
Date: Tue, 15 Jun 2010 09:17:12 +0200 [thread overview]
Message-ID: <20100615091712.2f41ce8f@surf> (raw)
In-Reply-To: <4c114469.104ddf0a.710f.1519@mx.google.com>
Hello,
Which skeleton are you moving to fs/skeleton/ ? The
target/generic/target_skeleton or
target/generic/target_busybox_skeleton ?
On Thu, 10 Jun 2010 22:58:30 +0300
Dmytro Milinevskyy <milinevskyy@gmail.com> wrote:
> rename {target/generic/target_busybox_skeleton/dev => fs/skeleton/bin}/.empty (100%)
I'm not sure what's happening here, but this rename (and many others)
look strange. Is it because all these .empty files are identical and
Git misdetects the renames ?
> rename {target/generic/target_busybox_skeleton => fs/skeleton}/etc/init.d/S20urandom (100%)
> rename {target/generic/target_busybox_skeleton => fs/skeleton}/etc/init.d/S40network (100%)
> rename {target/generic/target_busybox_skeleton => fs/skeleton}/etc/init.d/rcS (100%)
> rename {target/generic/target_skeleton => fs/skeleton}/etc/inittab (100%)
Some files renamed from target_busybox_skeleton, some others from
target_skeleton, strange. Is it also a strange Git behaviour because
the files are identical ?
Otherwise looks good,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-06-15 7:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 19:58 [Buildroot] [PATCH 1/2] [skeleton] move default skeleton to fs/ and drop busybox skeleton Dmytro Milinevskyy
2010-06-15 7:17 ` Thomas Petazzoni [this message]
2010-06-15 8:13 ` Dmytro Milinevskyy
2010-06-15 8:26 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2010-06-16 20:22 Dmytro Milinevskyy
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=20100615091712.2f41ce8f@surf \
--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.