git-new-workdir not working right?

git-new-workdir not working right?

[Caleb Cushing]

before I could do git-new-workdir path/to/repo/.git neworkdirname now
that doesn't seem to work... I actually had to cd to path/to/repo/.git
and do git-new-workdir . ../.../neworkdirname to get it to work. it
was complaining that the .git/ wasn't a git repo.

using git 1.6.2.3

-- 
Caleb Cushing

http://xenoterracide.blogspot.com

Re: git-new-workdir not working right?

[Julian Phillips]

On Tue, 14 Apr 2009, Caleb Cushing wrote:

> before I could do git-new-workdir path/to/repo/.git neworkdirname now
> that doesn't seem to work... I actually had to cd to path/to/repo/.git
> and do git-new-workdir . ../.../neworkdirname to get it to work. it
> was complaining that the .git/ wasn't a git repo.
>
> using git 1.6.2.3

Works fine for me.  Are you sure you didn't have a typo in your 
original git-new-workdir invocation?  If so, could you supply:

  1) the complete output of running git-new-workdir
  2) the output of "git rev-parse --git-dir" run in path/to/repo/.git

Also, you shouldn't need to supply the .git, so "git new-workdir 
path/to/repo newworkdirname" should also work, have you tried that?

-- 
Julian

  ---
Linux is addictive, I'm hooked!
 	-- MaDsen Wikholm's .sig

Re: git-new-workdir not working right?

[Caleb Cushing]

On Tue, Apr 14, 2009 at 10:47 AM, Julian Phillips
<julian@quantumfyre.co.uk> wrote:
> Works fine for me.  Are you sure you didn't have a typo in your original
> git-new-workdir invocation?  If so, could you supply:
>
>  1) the complete output of running git-new-workdir
>  2) the output of "git rev-parse --git-dir" run in path/to/repo/.git
>
> Also, you shouldn't need to supply the .git, so "git new-workdir
> path/to/repo newworkdirname" should also work, have you tried that?
>

git-new-workdir portage/ test
/home/port/portdev/.bin/git-new-workdir: line 58: cd:
/home/port/portdev/tree/portage
.git: No such file or directory
/home/port/portdev/tree/test
cp: cannot stat `/home/port/portdev/tree/HEAD': No such file or directory
fatal: Not a git repository (or any of the parent directories): .git

git-new-workdir portage/.git/ test
/home/port/portdev/.bin/git-new-workdir: line 58: cd:
/home/port/portdev/tree/portage/.git
.: No such file or directory
/home/port/portdev/tree/test
cp: cannot stat `/home/port/portdev/tree/HEAD': No such file or directory
fatal: Not a git repository (or any of the parent directories): .git

git rev-parse --git-dir portage/
fatal: Not a git repository (or any of the parent directories): .git

cd portage/
/home/port/portdev/tree/portage
slave-iv portage $ git rev-parse --git-dir .
.git
.

git-new-workdir . ../test/ << seems to work too.


-- 
Caleb Cushing

http://xenoterracide.blogspot.com

Re: git-new-workdir not working right?

[Julian Phillips]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1994 bytes --]

On Wed, 15 Apr 2009, Caleb Cushing wrote:

> On Tue, Apr 14, 2009 at 10:47 AM, Julian Phillips
> <julian@quantumfyre.co.uk> wrote:
>> Works fine for me.  Are you sure you didn't have a typo in your original
>> git-new-workdir invocation?  If so, could you supply:
>>
>>  1) the complete output of running git-new-workdir
>>  2) the output of "git rev-parse --git-dir" run in path/to/repo/.git
>>
>> Also, you shouldn't need to supply the .git, so "git new-workdir
>> path/to/repo newworkdirname" should also work, have you tried that?
>>
>
> git-new-workdir portage/ test
> /home/port/portdev/.bin/git-new-workdir: line 58: cd:
> /home/port/portdev/tree/portage
> .git: No such file or directory
> /home/port/portdev/tree/test
> cp: cannot stat `/home/port/portdev/tree/HEAD': No such file or directory
> fatal: Not a git repository (or any of the parent directories): .git
>
> git-new-workdir portage/.git/ test
> /home/port/portdev/.bin/git-new-workdir: line 58: cd:
> /home/port/portdev/tree/portage/.git
> .: No such file or directory
> /home/port/portdev/tree/test
> cp: cannot stat `/home/port/portdev/tree/HEAD': No such file or directory
> fatal: Not a git repository (or any of the parent directories): .git
>
> git rev-parse --git-dir portage/
> fatal: Not a git repository (or any of the parent directories): .git
>
> cd portage/
> /home/port/portdev/tree/portage
> slave-iv portage $ git rev-parse --git-dir .
> .git
> .
>
> git-new-workdir . ../test/ << seems to work too.
>

*sighs* oh yes, that old chestnut ...

You're exporting CDPATH, this variable shouldn't be exported.  This is 
likely to cause random shell scripts to break.

Alternatively, Putting "unset CDPATH" at the beginning of git-new-workdir 
should fix it.

This has come up a number of times in the past on the git list.  See, for 
example:

http://thread.gmane.org/gmane.comp.version-control.git/52177/focus=52268

-- 
Julian

  ---
English literature's performing flea.
 		-- Sean O'Casey on P.G. Wodehouse