From: Steven Grimm <koreth@midwinter.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Wink Saville <wink@saville.com>, git@vger.kernel.org
Subject: Re: Git branching & pulling
Date: Fri, 18 May 2007 23:22:28 -0700 [thread overview]
Message-ID: <464E97A4.4050702@midwinter.com> (raw)
In-Reply-To: <7vzm41xsa2.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> 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.
>
I do that all the time, e.g. when I'm syncing the satellite repo on my
laptop with the mothership repo in my account on my company's server.
The satellite only ever talks to the mothership and I am always
interested in pulling down all the changes I've committed to the
mothership during the day. So there's really no need to specify
anything; I always want to keep the two fully in sync, and there's never
any question about where I'm pulling from.
I do a plain "git pull" in my clone of git.git too. I want all the
latest updates and I'm only ever fetching them from the official git repo.
I can certainly imagine that if I were an integrator in charge of a
master repo, I'd always want to explicitly pull from particular places.
-Steve
next prev parent reply other threads:[~2007-05-19 6:22 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
2007-05-19 6:22 ` Steven Grimm [this message]
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=464E97A4.4050702@midwinter.com \
--to=koreth@midwinter.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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 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).