On Mon, Apr 17, 2017 at 7:03 PM, Junio C Hamano wrote:
> Jacob Keller writes:
>
>> From: Jacob Keller
>>
>> Don't assume that the current working directory is the root of the
>> repository. Correctly generate the path for the
On Mon, Apr 17, 2017 at 7:03 PM, Junio C Hamano wrote:
> Jacob Keller writes:
>
>> From: Jacob Keller
>>
>> Don't assume that the current working directory is the root of the
>> repository. Correctly generate the path for the
Jacob Keller writes:
> From: Jacob Keller
>
> Don't assume that the current working directory is the root of the
> repository. Correctly generate the path for the recursing child
> processes by building it from the work_tree() root instead.
On Thu, Apr 13, 2017 at 11:15 AM, Stefan Beller wrote:
> On Thu, Apr 13, 2017 at 10:12 AM, Jacob Keller
> wrote:
>> From: Jacob Keller
>>
>> Don't assume that the current working directory is the root of the
>> repository.
>
On Thu, Apr 13, 2017 at 10:12 AM, Jacob Keller wrote:
> From: Jacob Keller
>
> Don't assume that the current working directory is the root of the
> repository.
1) Oh! This bug might be hidden in other commands, too.
($ git grep cp.dir --
On 04/13, Jacob Keller wrote:
> From: Jacob Keller
>
> Don't assume that the current working directory is the root of the
> repository. Correctly generate the path for the recursing child
> processes by building it from the work_tree() root instead. Otherwise if
> we run
From: Jacob Keller
Don't assume that the current working directory is the root of the
repository. Correctly generate the path for the recursing child
processes by building it from the work_tree() root instead. Otherwise if
we run ls-files using --git-dir or --work-tree it
7 matches
Mail list logo