Not yet, I'm afraid. There are plans to create a deblobbed git repository tracking upstream, but we don't have the code to write a clean history so that we don't end up offering the very traps we set out to disarm.
This plan will require improvements to the deblobbing infrastructure that will enable us to fix the long-standing implementation bug that completely disables the blob-loading machinery. The intent is to avoid asking for blobs, but the Linux interface makes it hard to avoid that without also preventing users from loading the blobs if they really mean to. The solution for that is awkward, and not really achievable with the current deblobbing machinery.
There are also plans to improve git so as to enable back-and-forth merging between clean and blobful trees, to make cooperation easier without betraying our principles, but we're not there yet. We can always use help! More brains are welcome ;-P :-D
Posted Jul 25, 2012 8:02 UTC (Wed) by gioele (subscriber, #61675)
[Link]
> There are also plans to improve git so as to enable back-and-forth merging between clean and blobful trees,
Have you got any pointer to these plans? Such modifications to git would be very helpful to all the projects that maintain patches on top of git trees, think OpenWRT or all the Debian packages.
GNU Linux-libre 3.5-gnu: Free and a half
Posted Jul 25, 2012 9:45 UTC (Wed) by lindi (subscriber, #53135)
[Link]
Well I wanted git precisely to be able to observe the history. How the number of modifications to mainline change over time for example. I don't want to start unpacking hundreds of tarballs and running diff against them..