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

Re: git pull on Linux/ACPI release tree

From
MLMartin Langhoff <martin.langhoff-re5jqeeqqe8avxtiumwx3w@public.gmane.org>
Date
Jan 9, 2006, 04:34 UTC
Message-ID
<46a038f90601082034g2865b26ftc344c599e29a4655@mail.gmail.com>
In-Reply-To
<Pine.LNX.4.64.0601081909250.3169-hNm40g4Ew95AfugRpC6u6w@public.gmane.org>
On 1/9/06, Linus Torvalds <torvalds-3NddpPZAyC0@public.gmane.org> wrote:
Show 11 quoted lines
> And then do
>
>         git-rebase linus
>
> to rebase your development branch to mine.
>
> THIS is what "rebase" is for. It sounds like what you really want to do is
> not have a development branch at all, but you just want to track my tree
> and then keep track of a few branches of your own. In other words, you
> don't really have a "real" branch - you've got an odd collection of
> patches that you really want to carry around on top of _my_ branch. No?
FWIW, I determine whether I should rebase or merge based on
 + Whether the branch/head I maintain is public. For public repos, I
*must* merge carefully as rebase "rewinds" the head and that makes a
mess of any repositor tracking me.
 + Whether the changes on my both sides are significant, and it is
semantically meaningful to have a merge. If either side had just a
couple of minor commits, rebase makes life a lot easier down the path.
If both side clearly saw parallel development, it is more sincere to
merge and let that be recorded.
 + If my attempt to rebase leads to any non-trivial conflicts or
co-dependencies, then I definitely cancel the rebase and merge.
> Now, in this model, you're not really using git as a distributed system.

I'd argue that it is not about distributed or not. It's all in what you want to record in your history. As such, it is a communication device -- and I want to make effective use of it. I guess the question I ask myself is: what will communicate what's happened here most clearly? What will be useful for people to read? In that context, a white-lie here and there simplifying the history a bit where it's not interesting counts as a good thing.

cheers,

martin - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Previous: Adrian BunkNext: Linus Torvalds
Message 19 of 21 in “RE: git pull on Linux/ACPI release tree”
  1. Brown, LenJan 8, 2006
  2. Linus TorvaldsJan 8, 2006
  3. Martin LanghoffJan 8, 2006
  4. Linus TorvaldsJan 8, 2006
  5. David S. MillerJan 8, 2006
  6. Luben TuikovJan 8, 2006
  7. Linus TorvaldsJan 9, 2006
  8. Junio C HamanoJan 8, 2006
  9. Linus TorvaldsJan 8, 2006
  10. Tony LuckJan 8, 2006
  11. Adrian BunkJan 8, 2006
  12. Willy TarreauJan 8, 2006
  13. Linus TorvaldsJan 9, 2006
  14. Adrian BunkJan 10, 2006
  15. Martin LanghoffJan 10, 2006
  16. Andreas EricssonJan 11, 2006
  17. Greg KHJan 12, 2006
  18. Adrian BunkJan 13, 2006
  19. Martin LanghoffJan 9, 2006
  20. Linus TorvaldsJan 10, 2006
  21. Catalin MarinasJan 12, 2006

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.