Re: [Request] Git export with hardlinks

2013-02-11 Thread Jeff King
On Sun, Feb 10, 2013 at 11:33:26AM +0100, Thomas Koch wrote: > thank you very much for your idea! It's good and simple. It just breaks down > for the case when a large folder got renamed. Yes, it would never find renames, which a true sha1->path map could. > But I already hacked the basic layou

Re: [Request] Git export with hardlinks

2013-02-10 Thread Thomas Koch
Jeff King: > [...] > So a full checkout is 24M. For the next deploy, we'll start by asking > "cp" to duplicate the old, using hard links: Hi Jeff, thank you very much for your idea! It's good and simple. It just breaks down for the case when a large folder got renamed. But I already hacked the

Re: [Request] Git export with hardlinks

2013-02-08 Thread Jeff King
On Wed, Feb 06, 2013 at 04:19:07PM +0100, Thomas Koch wrote: > I'd like to script a git export command that can be given a list of already > exported worktrees and the tree SHA1s these worktrees correspond too. The git > export command should then for every file it wants to export lookup in the

[Request] Git export with hardlinks

2013-02-06 Thread Thomas Koch
Hi, I'd like to script a git export command that can be given a list of already exported worktrees and the tree SHA1s these worktrees correspond too. The git export command should then for every file it wants to export lookup in the existing worktrees whether an identical file is already presen