My copy of git was only one release behind the current release, but
updating seems to have fixed this issue. Thanks for the suggestion.
- Greg

On Jun 12, 2:39 am, Lee Hambley <[email protected]> wrote:
> Outdated version of Git on your machine?
> - Lee
>
> 2009/6/12 daBuzz <[email protected]>
>
>
>
> > When I run deploy using a local git repository the executing locally
> > line starting 'git clone...' throws an error. It looks like the first
> > command on the line seeing the third command's -b parameter and
> > rejecting it. The 'git clone...' line is valid and runs the three
> > commands without error in a DOS window or from ruby using `cmd.exe /
> > C`
>
> > Not sure where the issue is or what can be done to resolve it. Any
> > help would be appreciated.
>
> > F:\Data Files\Rails\myweb>cap deploy
> >  * executing `deploy'
> >  * executing `deploy:update'
> >  ** transaction: start
> >  * executing `deploy:update_code'
> >    executing locally: "git ls-remote Q:/git_files/myweb master"
> >  * getting (via checkout) revision
> > 9e3d1b72e59509fdb45f9aef2a6766bf5073deb1 to C:/DOCUME~1/user/LOC
> > ALS~1/Temp/20090611215307
> >    executing locally: git clone  Q:\git_files\myweb C:\DOCUME~1\user
> > \LOCALS~1\Temp\20090611215307 && cd /D C:\DOCUME~1\user\LOCALS~1\Temp
> > \20090611215307 && git checkout  -b deploy
> > 9e3d1b72e59509fdb45f9aef2a6766bf5073deb1
> > error: unknown switch `b'
> > usage: git clone [options] [--] <repo> [<dir>]
>
> >    -q, --quiet           be quiet
> >    -v, --verbose         be verbose
> >    -n, --no-checkout     don't create a checkout
> >    --bare                create a bare repository
> >    --naked               create a bare repository
> >    --mirror              create a mirror repository (implies bare)
> >    -l, --local           to clone from a local repository
> >    --no-hardlinks        don't use local hardlinks, always copy
> >    -s, --shared          setup as shared repository
> >    --template <path>     path the template repository
> >    --reference <repo>    reference repository
> >    -o, --origin <branch>
> >                          use <branch> instead of 'origin' to track
> > upstream
> >    -u, --upload-pack <path>
> >                          path to git-upload-pack on the remote
> >    --depth <depth>       create a shallow clone of that depth
>
> > *** [deploy:update_code] rolling back
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Capistrano" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.co.uk/group/capistrano?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to