git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Barry Roberts <blr@robertsr.us>
To: git@vger.kernel.org
Subject: git-gui clone differs from command line
Date: Wed, 28 May 2008 09:21:40 -0600	[thread overview]
Message-ID: <483D7884.2050407@robertsr.us> (raw)

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?


 From ssh://blr@cvs2/var/git/iv
 = [up to date]      master     -> origin/master
 = [up to date]      mbn/xtol   -> origin/mbn/xtol
 = [up to date]      sprint2    -> origin/sprint2
 = [up to date]      sprint3    -> origin/sprint3
 = [up to date]      sprint4    -> origin/sprint4
 = [up to date]      xtol       -> origin/xtol
You asked me to pull without telling me which branch you
want to merge with, and 'branch.master.merge' in
your configuration file does not tell me either.  Please
name which branch you want to merge on the command line and
try again (e.g. 'git pull <repository> <refspec>').
See git-pull(1) for details on the refspec.

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.

             reply	other threads:[~2008-05-28 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 15:21 Barry Roberts [this message]
2008-05-28 23:23 ` git-gui clone differs from command line Shawn O. Pearce
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=483D7884.2050407@robertsr.us \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).