Bug#681326: pristine-tar: Directly accessing .git directory

2018-04-27 Thread Ian Jackson
Ian Jackson writes ("Re: Bug#681326: pristine-tar: Directly accessing .git directory"): > *With* or *in* a worktree ? Anyway, I will try it and report back. I just tried it in a worktree. It worked. I think this means that either (i) this bug was fixed since pristine-tar 1.25

Bug#681326: pristine-tar: Directly accessing .git directory

2018-04-24 Thread Ian Jackson
Antonio Terceiro writes ("Re: Bug#681326: pristine-tar: Directly accessing .git directory"): > just tried private-tar with a worktree and AFAICT it just works. do you > have a specific test case that fails? *With* or *in* a worktree ? Anyway, I will try it and report back. My

Bug#681326: pristine-tar: Directly accessing .git directory

2018-04-23 Thread Antonio Terceiro
On Mon, Apr 23, 2018 at 01:49:29PM +0100, Ian Jackson wrote: > FYI, working trees generated by `git worktree' also have a file rather > than a directory as .git. So this bug in pristine-tar will stop it > working properly in those, too. > > Ie the problem is not limited to submodules. I mention

Bug#681326: pristine-tar: Directly accessing .git directory

2018-04-23 Thread Ian Jackson
FYI, working trees generated by `git worktree' also have a file rather than a directory as .git. So this bug in pristine-tar will stop it working properly in those, too. Ie the problem is not limited to submodules. I mention this because no-one in their right mind would use submodules :-) wherea