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

merge confusion

From
thepurpleblob <howardsmiller@googlemail.com>
Date
Jul 31, 2009, 12:35 UTC
Message-ID
<24755682.post@talk.nabble.com>

I had some unexpected behaviour doing a merge today. I wonder if anybody can tell me where I have gone wrong. This is the sequence...

* clone a remote repo
* created a local branch to track one of the remote branches
* did work on the local branch and then created another 'feature' branch
from that
* time elapsed and at some point(s) I pulled from the remote but did not
merge the original local branch
* finished feature, checkout local branch and merge in feature. 

What I didn't expect is that all the subsequent changes on the tracked remote branch got merged in too. Which I didn't want.

So the question is - is that what's supposed to happen (ie. if you do any merge the tracked branch 'fast forwards' the remote) and, if so, if I want a branch that stays a branch (doesn't ever merge with the remote) how would I do that?

Thanks!
-- 
View this message in context: http://www.nabble.com/merge-confusion-tp24755682p24755682.html
Sent from the git mailing list archive at Nabble.com.
Next: Allen Johnson
Message 1 of 5 in “merge confusion”
  1. thepurpleblobJul 31, 2009
  2. Allen JohnsonJul 31, 2009
  3. Sean EstabrooksJul 31, 2009
  4. Tim MazidOct 28, 2009
  5. Alex RiesenOct 28, 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.