Re: adding file by absolute name -- problem

From: Carlos Rica <jasampler@gmail.com>
Date: Apr 23, 2007, 13:39 UTC
Message-ID: <1b46aba20704230639k56fc1839qcad38f1e5ee0e238@mail.gmail.com>
In-Reply-To: <Pine.LNX.4.64.0704231215370.8822@racer.site>

Hi!

2007/4/23, Johannes Schindelin <Johannes.Schindelin@gmx.de>:

Show 10 quoted lines

> Hi,
>
> On Mon, 23 Apr 2007, Yakov Lerner wrote:
>
> > When I give absolute pathname /a/b/repo/d to git add, it
> > mostly does not work. I get errors from git-add. Is it by design ?
>
> AFAICT it is by design. I fail to see why absolute paths should be
> supported, too. You are supposed to be _in_ the working directory when
> adding files...

Since it is by design, a posible solution could be support an optional parameter to give the program the path of the directory (something as --dir /a/b). Then you could build a command line to be run from another place, without using absolute paths in the rest of parameters. Maybe it would be easier to implement by interested people. Anyway, I don't need this feature, too.

I think that if currently the program does not support absolute paths, this should be clearly stated in error messages and check for that in a centralized place.