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

Re: nicer frontend to get rebased tree?

From
Linus Torvalds <torvalds@linux-foundation.org>
Date
Aug 23, 2008, 17:58 UTC
Message-ID
<alpine.LFD.1.10.0808231054400.3363@nehalem.linux-foundation.org>
In-Reply-To
<20080823164546.GX23334@one.firstfloor.org>
On Sat, 23 Aug 2008, Andi Kleen wrote:
Show 7 quoted lines
> > 
> > A lot of the trees don't rebase. The rest of the trees may not realize 
> 
> That's not my experience, sorry (even on other other trees than linux-next,
> linux-next was just an example).  e.g. the original ACPI tree did it,
> the x86 tree jungle does it, most of the other architecture trees do it,
> the networking tree does it. etc.etc.

So _complain_ to those people. Tell them that they are making your life harder. Let them know.

I sure as hell let people know when they are making _my_ life harder. It has helped. The networking tree stopped rebasing, and the x86 tree doesn't do it for the topic branches (although I think it re-creates the "common" branches all the time, kind of like linux-next).

That said, why the hell do you even care? You shouldn't base your work on other trees anyway. You should base your work on something as stable as possible. IOW, not necessariyl even my "tree-of-the-day", but actually try to do as much development based on real releases as possible.

Yeah, sometimes you need to synchronize with other people, but that really should be avoided. Not because git doesn't do it well, but because any time you have multiple people working in the same area, there is something generally WRONG. It's indicative that there is a lack of modularity when people step on each others toes too much.

Show 5 quoted lines
> Then for linux-next it's reasonable to say that one shouldn't 
> do development on top of it, but still if there is supposed
> to be a tester base for it it requires at least reasonable
> support in git for regular read-only download and right now that
> support is at best obscure and unobvious (to avoid stronger words)
Umm. How obscure was it really to do
	git fetch
	git checkout
Hmm?
		Linus
Previous: Andi KleenNext: Ingo Molnar
Message 17 of 42 in “nicer frontend to get rebased tree?”
  1. Andi KleenAug 22, 2008
  2. Linus TorvaldsAug 22, 2008
  3. Andi KleenAug 22, 2008
  4. Linus TorvaldsAug 22, 2008
  5. Paolo CiarrocchiAug 22, 2008
  6. Linus TorvaldsAug 22, 2008
  7. Björn SteinbrinkAug 22, 2008
  8. Paolo CiarrocchiAug 22, 2008
  9. Linus TorvaldsAug 22, 2008
  10. Junio C HamanoAug 22, 2008
  11. Andi KleenAug 23, 2008
  12. Paolo BonziniAug 23, 2008
  13. Andi KleenAug 23, 2008
  14. Paolo BonziniAug 23, 2008
  15. Linus TorvaldsAug 23, 2008
  16. Andi KleenAug 23, 2008
  17. Linus TorvaldsAug 23, 2008
  18. Ingo MolnarAug 25, 2008
  19. Björn SteinbrinkAug 23, 2008
  20. Linus TorvaldsAug 23, 2008
  21. Björn SteinbrinkAug 23, 2008
  22. Documentating branches (was: nicer frontend to get rebased tree?)Marius Vollmer, Aug 23, 2008
  23. Miklos VajnaAug 23, 2008
  24. Marius VollmerAug 23, 2008
  25. Marius VollmerAug 23, 2008
  26. Avery PennarunAug 22, 2008
  27. Andi KleenAug 22, 2008
  28. Paolo CiarrocchiAug 22, 2008
  29. Jakub NarebskiAug 22, 2008
  30. Andi KleenAug 23, 2008
  31. Paolo CiarrocchiAug 23, 2008
  32. Jakub NarebskiAug 23, 2008
  33. Andi KleenAug 23, 2008
  34. Paolo CiarrocchiAug 23, 2008
  35. Linus TorvaldsAug 23, 2008
  36. Paolo CiarrocchiAug 23, 2008
  37. Björn SteinbrinkAug 23, 2008
  38. Junio C HamanoAug 24, 2008
  39. Jakub NarebskiAug 23, 2008
  40. Theodore TsoAug 23, 2008
  41. A proposed solution (Was: nicer frontend to get rebased tree?)Theodore Tso, Aug 23, 2008
  42. Mikael MagnussonAug 22, 2008

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.