Re: [PATCH v3 07/25] reflog: avoid constructing .lock path with git_path

Duy Nguyen writes: > On Wed, Feb 26, 2014 at 5:44 AM, Junio C Hamano wrote: >> Nguyễn Thái Ngọc Duy writes: >> >>> git_path() soon understands the path given to it. Some paths "abc" may >>> become "def" while other "ghi" may become "ijk". We don't want >>> git_path() to interfere with .lock pa

Re: [PATCH v3 07/25] reflog: avoid constructing .lock path with git_path

On Wed, Feb 26, 2014 at 5:44 AM, Junio C Hamano wrote: > Nguyễn Thái Ngọc Duy writes: > >> git_path() soon understands the path given to it. Some paths "abc" may >> become "def" while other "ghi" may become "ijk". We don't want >> git_path() to interfere with .lock path construction. Concatenate

Re: [PATCH v3 07/25] reflog: avoid constructing .lock path with git_path

Nguyễn Thái Ngọc Duy writes: > git_path() soon understands the path given to it. Some paths "abc" may > become "def" while other "ghi" may become "ijk". We don't want > git_path() to interfere with .lock path construction. Concatenate > ".lock" after the path has been resolved by git_path() so i

[PATCH v3 07/25] reflog: avoid constructing .lock path with git_path

git_path() soon understands the path given to it. Some paths "abc" may become "def" while other "ghi" may become "ijk". We don't want git_path() to interfere with .lock path construction. Concatenate ".lock" after the path has been resolved by git_path() so if "abc" becomes "def", we'll have "def.l