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

RE: fetch and pull

From
JDJohn Dlugosz <jdlugosz@tradestation.com>
Date
Mar 17, 2009, 16:44 UTC
Message-ID
<450196A1AAAE4B42A00A8B27A59278E70A3FC0A5@EXCHANGE.trad.tradestation.com>
In-Reply-To
<76718490903170921r36843c11y5aac537d53384298@mail.gmail.com>
Show 13 quoted lines
> On Tue, Mar 17, 2009 at 10:58 AM, John Dlugosz
> <JDlugosz@tradestation.com> wrote:
> >> $ git clone git://central/repo.git
> >> $ cd repo
> >> $ git checkout -b topic origin/master
> >> $ edit, commit, edit, commit, looks good
> >> $ git checkout master
> >> $ git pull
> >
> > You checkout master before updating it?
> 
> You cannot merge/rebase a branch unless it is checked out.
> 
Sure you can.
	git rebase upstream topic
But I think I see the point:  the implicit merge done by pull uses the current HEAD and config branch.<name>.merge.
My concern is that you establish your working state based on the local 'master', only to immediately change it again when the pull updates master.  But that's the way it's supposed to work?
I think the documentation for git-pull might also be garbled from text being of different eras.  "Normally the branch merged is the HEAD of the remote"?  That will be basically random since the last thing the upstream repo user did will control what his HEAD is.
But, the intention here is
  1) direct attention to the desired branch
  2) do what is appropriate for the current branch
The key to avoiding massive confusion is making sure that (2) is set up properly.  I never know what's going to happen with a pull, and I suppose that's because nothing was set up properly.
--John (still confused)
TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
Previous: Jay SoffianNext: Nanako Shiraishi
Message 12 of 19 in “Re: fetch and pull”
  1. John DlugoszMar 16, 2009
  2. Jay SoffianMar 16, 2009
  3. John DlugoszMar 16, 2009
  4. Sverre RabbelierMar 16, 2009
  5. Jeff KingMar 17, 2009
  6. Sverre RabbelierMar 17, 2009
  7. Jay SoffianMar 16, 2009
  8. John DlugoszMar 16, 2009
  9. Jay SoffianMar 17, 2009
  10. John DlugoszMar 17, 2009
  11. Jay SoffianMar 17, 2009
  12. John DlugoszMar 17, 2009
  13. Nanako ShiraishiMar 17, 2009
  14. Björn SteinbrinkMar 18, 2009
  15. Junio C HamanoMar 18, 2009
  16. John DlugoszMar 18, 2009
  17. Björn SteinbrinkMar 18, 2009
  18. John DlugoszMar 18, 2009
  19. Jeff KingMar 18, 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.