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

Re: nicer frontend to get rebased tree?

From
AKAndi Kleen <andi@firstfloor.org>
Date
Aug 23, 2008, 16:45 UTC
Message-ID
<20080823164546.GX23334@one.firstfloor.org>
In-Reply-To
<alpine.LFD.1.10.0808230853170.3363@nehalem.linux-foundation.org>
> Note that the "don't rebase" (as usual) only concerns your published tree. 
> You can certainly rebase non-published stuff.
> 
> As to the "don't base your development on somebody who does" - base your 

That's not practical for me. Maybe it's for you, but it doesn't really work if you're sufficiently down the food tree. You just have to work with what other maintainers have and you can't really yell at them when they do something inconvenient like you do all the time, because they just ignore you then.

Show 8 quoted lines
> development either on my tree (I don't rebase) or talk to the d*ck-head 
> that you _want_ to work with, but who rebases.
> 
> > > Remember how I told you that you should never rebase?
> > 
> > I suspect your recommendation does not match real world git use.
> 
> 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.

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)

> And linux-next has _never_ been appropriate as a development base for 
> other reasons, so forget about linux-next. It's to find merge conflicts 
> and possibly boot/test failures of the trees it contains, not for anything 
> else.

Well it sounds like most people except you get it "wrong". Or maybe it's more that your intended usage model just does not match what people really do.

-Andi 
Previous: Linus TorvaldsNext: Linus Torvalds
Message 16 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.