On Sat, 17 May 2008, Thomas Gleixner wrote:Listen to yourself. They are "topic" branches. They are supposed to do one thing. You keep them "uptodate" by doing your work on them, _not_ by merging everybody elses work into them. You _used_ to rebase. That hides bad workflows, because it hides the fact that your "topic branch" is not a topic branch at all, but something that tries to do much more than it's stated purpose. So now, when you stopped rebasing, the fact that you keep updating your topic branches with code that has nothing to do with your topic (ie code that I randomly merged from me) is visible as the unnecessary merges. Yes, doing a merge occasionally just to not fell *too* far behind is sane. But when you have twice as many merges as you have real commits, you're doing something wrong. At that point, you're no longer a topic branch, you're just a mess of other peoples development merged on top of random commits you do. See the difference? You literally merged four times in two days. That's not "keeping reasonably up-to-date", that's just messy and OCD. Linus --
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Randy Dunlap | Re: 2.6.25-mm1 (build error: driver core) |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Winkler, Tomas | RE: iwlwifi: fix build bug in "iwlwifi: fix LED stall" |
| Johann Baudy | Packet mmap: TX RING and zero copy |
