On Wed, 2008-05-28 at 19:23 -0400, Shawn O. Pearce wrote: > Barry Roberts <blr@xxxxxxxxxxx> wrote: > > After much mis-directed research, I finally figured out that cloning a > > repo (ssh://) with git-gui doesn't work exactly like 'git clone' from > > the command line. The main difference is that 'git pull' doesn't work > > on master. I get the error below. Is that intentional, or are we doing > > something wrong? > > Bug in git-gui. > > git-gui's clone feature isn't implemented in terms of git-clone. > Its implemented in terms of more primitive actions: > > git init > git remote add origin > git fetch > git fetch --tags > git update-ref refs/heads/master origin/master > git checkout > > however it forgets to setup the branch configuration: > > > If you often merge with the same branch, you may want to > > configure the following variables in your configuration > > file: > > > > branch.master.remote = <nickname> > > branch.master.merge = <remote-ref> > > remote.<nickname>.url = <url> > > remote.<nickname>.fetch = <refspec> > > > > See git-config(1) for details. > > Yea. That author of git-gui should really check git-config(1) > for detais. *ducks and hides* > > I'll try to fix it tonight or tomorrow. No worries. I just e-mailed out a [branch "master"] section from .git/config from a cmd-line clone'd repo and all the Windows users are happy. Oddly, our Linux users never saw this ;-) Thanks, Barry -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html