Bug#666033: pristine-tar can't handle new git submodules

Yes, that fixes it! Thanks. I was just about to try the same thing too. -matthaus On Tue, Mar 27, 2012 at 4:42 PM, Joey Hess wrote: > Matthaus Litteken wrote: >> This is likely due to a change in git's behavior in commit >> https://github.com/git/git/commit/501770e1bb5d132ae4f79aa96715f07f6b84e1

Bug#666033: pristine-tar can't handle new git submodules

Matthaus Litteken wrote: > This is likely due to a change in git's behavior in commit > https://github.com/git/git/commit/501770e1bb5d132ae4f79aa96715f07f6b84e1f6 > where submodules now have a git file and not a git directory. Yes, it checks -d. Could you try this patch? -- see shy jo diff --git

Bug#666033: pristine-tar can't handle new git submodules

Package: pristine-tar Version: 1.20 When I use pristine-tar in a git submodule that was cloned using git > 1.7.8, pristine-tar cannot determine the vcs of the repo. For example... $ mkdir test $ cd test $ git init Initialized empty Git repository $ git submodule add g...@github.com:user/project p