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

RFC: git pull or git rebase?

From
MTMichael S. Tsirkin <mst@dev.mellanox.co.il>
Date
Jul 23, 2007, 05:22 UTC
Message-ID
<20070723052223.GA20614@mellanox.co.il>
Hi!
I'm working on several kernel-related projects at the same time:
- some of them are small, and private, so I do a fetch
  and rebase to update to Linus' code, to keep history clean
- some of them are larger, and involve several other people,
  so I do git pull (the history is messy anyway)

Problem is, I get confused sometimes and do a git pull instead of git rebase, or vice versa. Of course I can just reset to ORIG_HEAD when I realise my mistake.

However, I wonder whether this happens to others, too. Would it make sense to add a branch attribute that says "do not pull this branch" or "do not rebase this branch"? Maybe even make git do the right thing automatically, so that git would look at this attribute and perform pull or rebase as appropriate?

Thanks,
-- 
MST
Next: Alex Riesen
Message 1 of 3 in “RFC: git pull or git rebase?”
  1. Michael S. TsirkinJul 23, 2007
  2. Alex RiesenJul 23, 2007
  3. Michael S. TsirkinJul 23, 2007

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.