All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Barry Roberts <blr@robertsr.us>
Cc: git@vger.kernel.org
Subject: Re: git-gui clone differs from command line
Date: Wed, 28 May 2008 19:23:24 -0400	[thread overview]
Message-ID: <20080528232324.GM30245@spearce.org> (raw)
In-Reply-To: <483D7884.2050407@robertsr.us>

Barry Roberts <blr@robertsr.us> 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.

-- 
Shawn.

  reply	other threads:[~2008-05-28 23:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 15:21 git-gui clone differs from command line Barry Roberts
2008-05-28 23:23 ` Shawn O. Pearce [this message]
2008-05-29  2:59   ` Barry Roberts
2008-05-29 13:40     ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080528232324.GM30245@spearce.org \
    --to=spearce@spearce.org \
    --cc=blr@robertsr.us \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.