{"thread":{"id":"18862","subject":"git-new-workdir not working right?","startedAt":"2009-04-14T04:09:43Z","lastAt":"2009-04-15T12:22:48Z","messageCount":4,"participants":["Caleb Cushing","Julian Phillips"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"111258","messageId":"81bfc67a0904132109k45f09f79s21ce3132ade02001@mail.gmail.com","threadId":"18862","inReplyTo":null,"subject":"git-new-workdir not working right?","fromName":"Caleb Cushing","fromEmail":"xenoterracide@gmail.com","sentAt":"2009-04-14T04:09:43Z","receivedAt":"2009-04-14T04:09:43Z","isPatch":false,"sender":{"key":"xenoterracide@gmail.com","avatar":"https://gravatar.com/avatar/af3f0745dfa0ea9c4ee551d7d0a3cfe7ba8d229754c11678ab2ed23c3fa57065?d=mp&s=160"},"body":"before I could do git-new-workdir path/to/repo/.git neworkdirname now\nthat doesn't seem to work... I actually had to cd to path/to/repo/.git\nand do git-new-workdir . ../.../neworkdirname to get it to work. it\nwas complaining that the .git/ wasn't a git repo.\n\nusing git 1.6.2.3\n\n-- \nCaleb Cushing\n\nhttp://xenoterracide.blogspot.com\n"},{"id":"111288","messageId":"alpine.LNX.2.00.0904141540410.29027@reaper.quantumfyre.co.uk","threadId":"18862","inReplyTo":"81bfc67a0904132109k45f09f79s21ce3132ade02001@mail.gmail.com","subject":"Re: git-new-workdir not working right?","fromName":"Julian Phillips","fromEmail":"julian@quantumfyre.co.uk","sentAt":"2009-04-14T14:47:58Z","receivedAt":"2009-04-14T14:47:58Z","isPatch":false,"sender":{"key":"julian@quantumfyre.co.uk","avatar":"https://avatars.githubusercontent.com/u/948888?v=4"},"body":"On Tue, 14 Apr 2009, Caleb Cushing wrote:\n\n> before I could do git-new-workdir path/to/repo/.git neworkdirname now\n> that doesn't seem to work... I actually had to cd to path/to/repo/.git\n> and do git-new-workdir . ../.../neworkdirname to get it to work. it\n> was complaining that the .git/ wasn't a git repo.\n>\n> using git 1.6.2.3\n\nWorks fine for me.  Are you sure you didn't have a typo in your \noriginal git-new-workdir invocation?  If so, could you supply:\n\n  1) the complete output of running git-new-workdir\n  2) the output of \"git rev-parse --git-dir\" run in path/to/repo/.git\n\nAlso, you shouldn't need to supply the .git, so \"git new-workdir \npath/to/repo newworkdirname\" should also work, have you tried that?\n\n-- \nJulian\n\n  ---\nLinux is addictive, I'm hooked!\n \t-- MaDsen Wikholm's .sig\n"},{"id":"111350","messageId":"81bfc67a0904150331t6787fcfbjd391013a8235ece0@mail.gmail.com","threadId":"18862","inReplyTo":"alpine.LNX.2.00.0904141540410.29027@reaper.quantumfyre.co.uk","subject":"Re: git-new-workdir not working right?","fromName":"Caleb Cushing","fromEmail":"xenoterracide@gmail.com","sentAt":"2009-04-15T10:31:04Z","receivedAt":"2009-04-15T10:31:04Z","isPatch":false,"sender":{"key":"xenoterracide@gmail.com","avatar":"https://gravatar.com/avatar/af3f0745dfa0ea9c4ee551d7d0a3cfe7ba8d229754c11678ab2ed23c3fa57065?d=mp&s=160"},"body":"On Tue, Apr 14, 2009 at 10:47 AM, Julian Phillips\n<julian@quantumfyre.co.uk> wrote:\n> Works fine for me.  Are you sure you didn't have a typo in your original\n> git-new-workdir invocation?  If so, could you supply:\n>\n>  1) the complete output of running git-new-workdir\n>  2) the output of \"git rev-parse --git-dir\" run in path/to/repo/.git\n>\n> Also, you shouldn't need to supply the .git, so \"git new-workdir\n> path/to/repo newworkdirname\" should also work, have you tried that?\n>\n\ngit-new-workdir portage/ test\n/home/port/portdev/.bin/git-new-workdir: line 58: cd:\n/home/port/portdev/tree/portage\n.git: No such file or directory\n/home/port/portdev/tree/test\ncp: cannot stat `/home/port/portdev/tree/HEAD': No such file or directory\nfatal: Not a git repository (or any of the parent directories): .git\n\ngit-new-workdir portage/.git/ test\n/home/port/portdev/.bin/git-new-workdir: line 58: cd:\n/home/port/portdev/tree/portage/.git\n.: No such file or directory\n/home/port/portdev/tree/test\ncp: cannot stat `/home/port/portdev/tree/HEAD': No such file or directory\nfatal: Not a git repository (or any of the parent directories): .git\n\ngit rev-parse --git-dir portage/\nfatal: Not a git repository (or any of the parent directories): .git\n\ncd portage/\n/home/port/portdev/tree/portage\nslave-iv portage $ git rev-parse --git-dir .\n.git\n.\n\ngit-new-workdir . ../test/ << seems to work too.\n\n\n-- \nCaleb Cushing\n\nhttp://xenoterracide.blogspot.com\n"},{"id":"111356","messageId":"alpine.LNX.2.00.0904151310140.11773@reaper.quantumfyre.co.uk","threadId":"18862","inReplyTo":"81bfc67a0904150331t6787fcfbjd391013a8235ece0@mail.gmail.com","subject":"Re: git-new-workdir not working right?","fromName":"Julian Phillips","fromEmail":"julian@quantumfyre.co.uk","sentAt":"2009-04-15T12:22:48Z","receivedAt":"2009-04-15T12:22:48Z","isPatch":false,"sender":{"key":"julian@quantumfyre.co.uk","avatar":"https://avatars.githubusercontent.com/u/948888?v=4"},"body":"On Wed, 15 Apr 2009, Caleb Cushing wrote:\n\n> On Tue, Apr 14, 2009 at 10:47 AM, Julian Phillips\n> <julian@quantumfyre.co.uk> wrote:\n>> Works fine for me.  Are you sure you didn't have a typo in your original\n>> git-new-workdir invocation?  If so, could you supply:\n>>\n>>  1) the complete output of running git-new-workdir\n>>  2) the output of \"git rev-parse --git-dir\" run in path/to/repo/.git\n>>\n>> Also, you shouldn't need to supply the .git, so \"git new-workdir\n>> path/to/repo newworkdirname\" should also work, have you tried that?\n>>\n>\n> git-new-workdir portage/ test\n> /home/port/portdev/.bin/git-new-workdir: line 58: cd:\n> /home/port/portdev/tree/portage\n> .git: No such file or directory\n> /home/port/portdev/tree/test\n> cp: cannot stat `/home/port/portdev/tree/HEAD': No such file or directory\n> fatal: Not a git repository (or any of the parent directories): .git\n>\n> git-new-workdir portage/.git/ test\n> /home/port/portdev/.bin/git-new-workdir: line 58: cd:\n> /home/port/portdev/tree/portage/.git\n> .: No such file or directory\n> /home/port/portdev/tree/test\n> cp: cannot stat `/home/port/portdev/tree/HEAD': No such file or directory\n> fatal: Not a git repository (or any of the parent directories): .git\n>\n> git rev-parse --git-dir portage/\n> fatal: Not a git repository (or any of the parent directories): .git\n>\n> cd portage/\n> /home/port/portdev/tree/portage\n> slave-iv portage $ git rev-parse --git-dir .\n> .git\n> .\n>\n> git-new-workdir . ../test/ << seems to work too.\n>\n\n*sighs* oh yes, that old chestnut ...\n\nYou're exporting CDPATH, this variable shouldn't be exported.  This is \nlikely to cause random shell scripts to break.\n\nAlternatively, Putting \"unset CDPATH\" at the beginning of git-new-workdir \nshould fix it.\n\nThis has come up a number of times in the past on the git list.  See, for \nexample:\n\nhttp://thread.gmane.org/gmane.comp.version-control.git/52177/focus=52268\n\n-- \nJulian\n\n  ---\nEnglish literature's performing flea.\n \t\t-- Sean O'Casey on P.G. Wodehouse"}]}