git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: fetch and pull

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 6, 2009, 20:49 UTC
Message-ID
<7vd4cus7ez.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<m3iqmmidlf.fsf@localhost.localdomain>
Jakub Narebski <jnareb@gmail.com> writes:
Show 26 quoted lines
> "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...

I do not think it has much to do with the main point of what John wants to do which is to muck with local branch without checking it out, which is only possible when it happens to fast forward to the new tip of the corresponding branch obtained from the the remote.

Previous: Jakub NarebskiNext: John Dlugosz
Message 4 of 10 in “fetch and pull”
  1. John DlugoszMar 6, 2009
  2. Junio C HamanoMar 6, 2009
  3. Jakub NarebskiMar 6, 2009
  4. Junio C HamanoMar 6, 2009
  5. John DlugoszMar 6, 2009
  6. Junio C HamanoMar 6, 2009
  7. Bryan DonlanMar 7, 2009
  8. Junio C HamanoMar 7, 2009
  9. John DlugoszMar 9, 2009
  10. John DlugoszMar 9, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.