On Mon, Feb 10, 2014 at 11:55 PM, Torsten Bögershausen <tbo...@web.de> wrote:
> On 2014-02-10 11.37, Duy Nguyen wrote:
>>> Could we use relative path names internally, relative to $GIT_DIR ?
>> No because this is when the client tell the server about $GIT_DIR. I
>> guess we can use realpath(1) here.
> Good.
> I realized that the watcher can watch several repos at the same time.
> However, we could allow relative path names, which will be relative to 
> and loosen the demand for an absolut path name a little bit.
> And $SOCKET_DIR can be the same as $GIT_DIR, when we are watching only one 
> repo.

It does not help much anyway because file-watcher-lib.c sends
get_git_work_tree(), which is absolute/normalized path, to
file-watcher. There's no sources of sending $GIT_DIR relative to
$SOCKET_DIR (and I don't think we want to make get_git_work_tree()
relative before sending, it's more work on both sides we no benefits,
except for tracing).
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