[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130725215315.GV7729@decadent.org.uk>
Date: Thu, 25 Jul 2013 22:53:15 +0100
From: Ben Hutchings <ben@...adent.org.uk>
To: Jason Cooper <jason@...edaemon.net>
Cc: Rob Herring <robherring2@...il.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"ksummit-2013-discuss@...ts.linuxfoundation.org"
<ksummit-2013-discuss@...ts.linuxfoundation.org>,
Russell King - ARM Linux <linux@....linux.org.uk>,
Domenico Andreoli <cavokz@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Dave P Martin <Dave.Martin@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [Ksummit-2013-discuss] DT bindings as ABI [was: Do we have
people interested in device tree janitoring / cleanup?]
On Thu, Jul 25, 2013 at 04:32:28PM -0400, Jason Cooper wrote:
[...]
> One of the things I've been trying to square up in my head is how to
> retain the history of the binding when moving to the new tree. My
> current idea was to clone the kernel tree, add one patch deleting
> everything but the bindings and dts files, and one more patch moving
> things where we want them (arch/{powerpc,arm}/boot/dts -> dts).
>
> Then, as needed, we could merge a kernel version tag and delete
> everything we don't need (code) in the merge commit.
>
> The downside of this is it would be messy, the upside is that we could
> closely track the kernel tree (until the bindings and dts are moved
> out), and retain the history of the bindings and dts files.
[...]
It's *extremely* messy, but 'git filter-branch' might help to make a
clean tracking branch preserving history of just DT files. David
Woodhouse did something like that for the linux-firmware repo
initially.
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists