Re: Finding the repository

2013-10-24 Thread Phil Hord
On Thu, Oct 24, 2013 at 9:46 AM, Duy Nguyen wrote: > On Thu, Oct 24, 2013 at 2:49 PM, Perry Hutchison > wrote: >> Duy Nguyen wrote: >> >>> ... it's not easy to determine ambiguity here, especially when the >>> repo finding code does not know anything about "bar/barz.c" (is it >>> a pathname or

Re: Finding the repository

2013-10-24 Thread Duy Nguyen
On Thu, Oct 24, 2013 at 2:49 PM, Perry Hutchison wrote: > Duy Nguyen wrote: > >> ... it's not easy to determine ambiguity here, especially when the >> repo finding code does not know anything about "bar/barz.c" (is it >> a pathname or an argument to an option?). > > IOW, the code that finds the r

Re: Finding the repository

2013-10-24 Thread Perry Hutchison
Duy Nguyen wrote: > ... it's not easy to determine ambiguity here, especially when the > repo finding code does not know anything about "bar/barz.c" (is it > a pathname or an argument to an option?). IOW, the code that finds the repository is called "too early"? One way to solve that to that wo

Re: Finding the repository

2013-10-23 Thread Duy Nguyen
On Wed, Oct 23, 2013 at 2:52 PM, Perry Hutchison wrote: > At least in version 1.7.0.4, it seems git does not like being run > from outside the repository, even if the file(s) being operated > on are inside the repository, unless it is given a pointer to the > repository via the --git-dir= option o

Finding the repository

2013-10-23 Thread Perry Hutchison
At least in version 1.7.0.4, it seems git does not like being run from outside the repository, even if the file(s) being operated on are inside the repository, unless it is given a pointer to the repository via the --git-dir= option or the GIT_DIR enironment variable. For example, suppose /foo/bar