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

Re: how to check what your pulling down?

From
Matthieu Moy <matthieu.moy@imag.fr>
Date
Apr 16, 2009, 17:03 UTC
Message-ID
<vpq7i1kttss.fsf@bauges.imag.fr>
In-Reply-To
<7vfxg8k0mk.fsf@gitster.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 10 quoted lines
> cantona <adam@dwpub.com> writes:
>
>> I've been using basic git for a while (add,comit,push,pull) and have
>> recently discovered stash,merge,branch :)
>>
>> My question: before I pull down I always get that bad feeling... "what am i
>> gunna get? will there be a conflict?".
>
> "will there be a conflict?" is an unfounded fear people seem to be unable
> to shake off from their old scm days.

But still, if you want to know what's new without touching your work at all, "git fetch" is your friend: it fetches new commits from another repository, without merging them with your branches. Running "gitk --all" right after a "git fetch" should help understanding what it did.

-- 
Matthieu
Previous: Junio C Hamano
Message 4 of 4 in “how to check what your pulling down?”
  1. cantonaApr 16, 2009
  2. Jeff KingApr 16, 2009
  3. Junio C HamanoApr 16, 2009
  4. Matthieu MoyApr 16, 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.