From: Jakub Narebski <jnareb@gmail.com>
To: "John Dlugosz" <JDlugosz@TradeStation.com>
Cc: <git@vger.kernel.org>
Subject: Re: fetch and pull
Date: Fri, 06 Mar 2009 12:44:49 -0800 (PST) [thread overview]
Message-ID: <m3iqmmidlf.fsf@localhost.localdomain> (raw)
In-Reply-To: <450196A1AAAE4B42A00A8B27A59278E70A115E0D@EXCHANGE.trad.tradestation.com>
"John Dlugosz" <JDlugosz@TradeStation.com> writes:
> So, after inspecting the changes, how do you fast-forward your local dev
> to sync up with origin/dev?
>
> I'm worried that
>
> git pull origin dev
>
> will try to merge into the current head. The documentation indicates
> "The remote ref that matches <src> is fetched, and if <dst> is not empty
> string, the local ref that matches it is fast forwarded using <src>."
> which is what I want, but it does NOT say that the normal behavior of
> merging origin/dev into the =current= HEAD, if it happens to not be the
> local dev.
>
> So, does it indeed suppress that behavior if you give it an explicit
> destination? Or will I have to checkout dev first before doing the
> pull, to prevent strange things from happening? Hmm, or perhaps I
> should be using merge, not pull? After all, pull is really just a
> wrapper around fetch and then merge, right? So is it OK to call merge
> when I really want to fast-forward, and is there an option to give an
> error if it isn't ff?
There was patch series adding support --ff=only, but I think it didn't
made into git... Hmmm...
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-03-06 20:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 19:04 fetch and pull John Dlugosz
2009-03-06 19:27 ` Junio C Hamano
2009-03-06 20:44 ` Jakub Narebski [this message]
2009-03-06 20:49 ` Junio C Hamano
2009-03-06 22:11 ` John Dlugosz
2009-03-06 22:21 ` Junio C Hamano
2009-03-07 8:00 ` Bryan Donlan
2009-03-07 20:15 ` Junio C Hamano
2009-03-09 15:27 ` John Dlugosz
2009-03-09 15:08 ` John Dlugosz
[not found] <AcmmaYOKDtJohyDSQt2B3xvVeIPNPw==>
2009-03-16 19:00 ` John Dlugosz
2009-03-16 20:03 ` Jay Soffian
2009-03-16 20:39 ` John Dlugosz
2009-03-16 20:43 ` Sverre Rabbelier
2009-03-17 8:34 ` Jeff King
2009-03-17 8:36 ` Sverre Rabbelier
2009-03-16 22:14 ` Jay Soffian
2009-03-16 22:33 ` John Dlugosz
2009-03-17 0:09 ` Jay Soffian
2009-03-17 14:58 ` John Dlugosz
2009-03-17 16:21 ` Jay Soffian
2009-03-17 16:44 ` John Dlugosz
2009-03-17 21:31 ` Nanako Shiraishi
2009-03-18 8:58 ` Björn Steinbrink
2009-03-18 9:37 ` Junio C Hamano
2009-03-18 15:18 ` John Dlugosz
2009-03-18 15:31 ` Björn Steinbrink
2009-03-18 16:50 ` John Dlugosz
2009-03-18 0:37 ` Jeff King
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=m3iqmmidlf.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=JDlugosz@TradeStation.com \
--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).