From: Junio C Hamano <junkio@cox.net>
To: "Wink Saville" <wink@saville.com>
Cc: git@vger.kernel.org
Subject: Re: Git branching & pulling
Date: Fri, 18 May 2007 23:05:09 -0700 [thread overview]
Message-ID: <7vzm41xsa2.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7v8xblz71o.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Fri, 18 May 2007 23:00:51 -0700")
Junio C Hamano <junkio@cox.net> writes:
> "Wink Saville" <wink@saville.com> writes:
>
>> Could someone give me some insight or point me at a url or doc
>> that could shed some light on what is happening and why git-pull
>> doesn't work on kvm.git.
>
> DEFAULT BEHAVIOUR section of
>
> http://www.kernel.org/pub/software/scm/git/docs/git-pull.html
>
> would be the place to start. Recent git-clone (post 1.5.0, I think)
> prepares the following configuration variables for you by default:
>
> remote.origin.url
> remote.origin.fetch
> branch.master.remote
> branch.master.merge
>
> but repositories created by older git-clone didn't.
/me says "oops I did not finish the sentence".
but repositories created by older git-clone didn't get these
configuration variables set. If you set them appropriately,
taking example of your other repository (and probably you would
also want to remove .git/remotes/origin while you are at it),
you can omit saying which branch to pull from where.
I personally never understood why people would just want to say
"git pull" without saying anything else, but what described in
the DEFAULT BEHAVIOUR section is how it works.
next prev parent reply other threads:[~2007-05-19 6:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 5:40 Git branching & pulling Wink Saville
2007-05-19 5:49 ` J. Bruce Fields
2007-05-19 6:00 ` Junio C Hamano
2007-05-19 6:05 ` Junio C Hamano [this message]
2007-05-19 6:22 ` Steven Grimm
2007-05-19 6:28 ` Junio C Hamano
2007-05-19 16:31 ` Wink Saville
2007-05-20 20:30 ` Josef Weidendorfer
2007-05-23 0:22 ` Wink Saville
2007-05-23 0:35 ` Junio C Hamano
2007-05-23 5:07 ` [PATCH] Document branch.autosetupmerge Paolo Bonzini
2007-05-23 9:49 ` Git branching & pulling Josef Weidendorfer
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=7vzm41xsa2.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=wink@saville.com \
/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.