On Sat, Dec 18, 2010 at 11:19 PM, Alexandre Oliva <[email protected]> wrote:
> I'd like very much to have this implemented in time for 2.6.38 (late > Mar/early Apr 2011, considering that 2.6.37 should be out by late > Dec/early Jan), and I'd love to have this in a git repository rather > than as deblobbing scripts, but a solution for the problem of creating a > git repository that can track Linux upstream without carrying the > non-Free bits that the Linux git repository carries has so far eluded > me. Any git experts willing to contribute expertise to this end? Or > perhaps users of other git-compatible DVCS that could help us get the > behavior we need? Say, if bzr could track Linux git repos while > enabling us to filter out the non-Free bits from the history, we might > solve our problem and promote a GNU DVCS at the same time. Asked a friend who is a git expert; sorry if this is duplicative at this point, but: ---------- Forwarded message ---------- From: Michael Stone <[email protected]> Date: Sun, Jan 9, 2011 at 3:14 PM Subject: Re: git expert question from GNU-linux-libre list To: Daniel Clark <[email protected]> Cc: Bernie Innocenti <[email protected]> You need some way to mechanically identify non-free blobs that you want to remove. Once you've got that, you can write a "kill-nonfree-blobs" program. Then, you can use some adaptation of git-filter-branch [1] like so: git filter-branch --tree-filter kill-nonfree-blobs ... with a cronjob to keep your repository up to date. Regards, Michael [1]: http://www.kernel.org/pub/software/scm/git/docs/git-filter-branch.html P.S. - @Bernie: Other ideas? On 1/9/11, Daniel Clark <[email protected]> wrote: > Thought one of you might have an idea on this... > > -- > \|/ Daniel JB Clark | Activist; Owner > FREEDOM -+-> INCLUDED ~ http://freedomincluded.com > /|\ Free Software respecting hardware
