From: David Woodhouse <dwmw2@infradead.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Merge dtc
Date: Tue, 04 Dec 2007 17:22:39 +0000 [thread overview]
Message-ID: <1196788959.13978.358.camel@pmac.infradead.org> (raw)
In-Reply-To: <20071204031027.GJ32577@localhost.localdomain>
On Tue, 2007-12-04 at 14:10 +1100, David Gibson wrote:
> We've been back and forth on this several times, Paul and I finally
> concluded this was the better option.
As long as I can just ignore it and use the separately-shipped dtc, I
suppose it doesn't have to bother me too much.
> It means we can feel free to use dtc for whatever new platforms we
> wish to without people whinging about having to install a new tool.
I think we're overestimating this 'problem'; really.
But anyway, if we have to go ahead with it, can we make sure we keep in
sync with the 'real' dtc? One way of doing that is as follows...
It's not hard to make a git repository which is a simple 'transform' of
another tree -- I have a couple, at
http://git.infradead.org/?p=users/dwmw2/jffs2-ecos-core.git and
http://git.kernel.org/?p=linux/kernel/git/dwmw2/kernel-headers.git
The scripts to generate those are at
http://david.woodhou.se/extract-jffs2-git.sh
http://david.woodhou.se/extract-khdrs-git.sh
http://david.woodhou.se/extract-khdrs-stage2.sh
(The kernel headers one is in two stages because it has to mangle the
files through unifdef too).
I'm sure there are better ways of doing it, but the scripts I have work,
and should hopefully serve as a vaguely useful example.
I'd recommend making such a 'transform' which tracks the upstream dtc
tree but with the files you want moved into the correct places. Then all
we have to do to update the kernel's copy is pull from that transformed
tree.
Of course, it's possible that git has matured to the point where it can
handle the 'renames' and you can just pull from the upstream dtc
repository directly. I don't think that's the case though.
--
dwmw2
next prev parent reply other threads:[~2007-12-04 17:22 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 5:02 Merge dtc David Gibson
2007-10-16 5:08 ` Kumar Gala
2007-10-16 5:18 ` David Gibson
2007-10-16 5:39 ` Paul Mackerras
2007-10-16 5:50 ` Kumar Gala
2007-10-16 6:01 ` Benjamin Herrenschmidt
2007-10-16 6:23 ` Kumar Gala
2007-10-16 10:53 ` Josh Boyer
2007-10-17 19:59 ` Timur Tabi
2007-10-17 20:12 ` Josh Boyer
2007-10-17 20:31 ` Grant Likely
2007-10-17 21:42 ` Linas Vepstas
2007-10-17 21:51 ` Jon Loeliger
2007-10-16 6:00 ` Benjamin Herrenschmidt
2007-10-16 6:24 ` Kumar Gala
2007-10-16 13:17 ` Grant Likely
2007-10-16 13:41 ` Kumar Gala
2007-10-17 5:22 ` David Gibson
2007-10-17 13:15 ` Grant Likely
2007-10-17 16:22 ` Stephen Neuendorffer
2007-12-04 1:59 ` David Woodhouse
2007-12-04 3:10 ` David Gibson
2007-12-04 17:22 ` David Woodhouse [this message]
2007-12-04 13:25 ` Jon Loeliger
2007-12-04 15:26 ` Josh Boyer
2007-12-04 16:04 ` Kumar Gala
2007-12-04 22:12 ` David Gibson
2007-12-04 16:08 ` Scott Wood
2007-12-04 22:21 ` Paul Mackerras
2007-12-04 22:33 ` David Woodhouse
2007-12-05 0:54 ` David Woodhouse
2007-12-05 1:49 ` Josh Boyer
2007-12-05 1:09 ` Paul Mackerras
2007-12-04 22:34 ` Josh Boyer
2007-12-05 2:22 ` Paul Mackerras
2007-12-05 2:26 ` Josh Boyer
2007-12-05 4:00 ` Josh Boyer
2007-12-05 4:37 ` Olof Johansson
-- strict thread matches above, loose matches on Subject: below --
2007-10-18 17:49 Milton Miller
2007-10-18 19:59 ` Sam Ravnborg
2007-10-19 1:45 ` David Gibson
2007-10-19 5:56 ` Milton Miller
2007-10-19 6:55 ` David Gibson
2007-10-19 7:07 ` Sam Ravnborg
2007-10-19 7:10 ` David Gibson
2007-10-19 18:42 ` Sam Ravnborg
2007-10-31 2:45 ` David Gibson
2007-11-08 13:59 ` Jon Loeliger
2007-10-19 1:30 ` David Gibson
2007-10-19 5:34 ` Milton Miller
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=1196788959.13978.358.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).