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, 19:27 UTC
Message-ID
<7vljrisb7u.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<450196A1AAAE4B42A00A8B27A59278E70A115E0D@EXCHANGE.trad.tradestation.com>
"John Dlugosz" <JDlugosz@TradeStation.com> writes:
Show 17 quoted lines
> I've gotten the hang of git well enough to pretty much bang on it until
> I achieve what I wanted to happen, though maybe trying a few things and
> recovering from mistakes or taking the long way around.
>
> Now I'm putting together a cookbook for our team, to allow use of topic
> branches rather than treating it simply as a faster SourceSafe.
>
> I want to advocate running
>
> 	git fetch
>
> as being a safe thing to do at any time, just to refresh your view of
> the origin and not mess up any of your local labels.  That is, you can
> see the difference between the local dev and the origin/dev.
>
> So, after inspecting the changes, how do you fast-forward your local dev
> to sync up with origin/dev?
$ git push . origin/dev dev
Previous: John DlugoszNext: Jakub Narebski
Message 2 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.