On Wed, Feb 26, 2014 at 5:44 AM, Junio C Hamano <gits...@pobox.com> wrote:
> Nguyễn Thái Ngọc Duy  <pclo...@gmail.com> 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 if "abc"
>> becomes "def", we'll have "def.lock", not "ijk".
> Hmph.  I am not sure if the above is readable (or if I am reading it
> correctly).

Definitely not now that I have had my break from the series and reread it.

> If "abc" becomes "def", it would take deliberate work to make
> "abc.lock" into "ijk", and it would be natural to expect that
> "abc.lock" would become "def.lock" without any fancy trick, no?

A better explanation may be, while many paths are not converted by
git_path() ("abc" -> "abc"), some of them will be based on the given
path ("def" -> "ghi"). Giving path def.lock to git_path() may confuse
it and make it believe def.lock should not be converted because the
signature is "def.lock" not "def". But we want the lock file to have
the same base name with the locked file (e.g. "ghi.lock", not
"def.lock"). So it's best to append ".lock" after git_path() has done
its conversion.

The alternative is teach git_path about ".lock", but I don't really
want to put more logic down there.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to