Hello, On Jan 18, 2008 4:55 PM, Steven Rostedt <rostedt@goodmis.org> wrote:Well not exactly. Unlike the mm tree which is made of a lots of patches dealing with totaly unrelated subjects, the rt patches only hopefully deal with realtime stuffs. I'm probably missing something since I haven't looked at the RT patches (yet) but couldn't these 300 patches be sorted out by topics ? If so you could create a branch per topic and merge all of them in your master branch which would be the rt kernel. Hopefully each branch won't interact with other branch too much. All of this assumes of course that the number of topics is definitely much smaller than the number of patches (~300). Having such a tree would be very useful for looking at history in each topic, for doing some git-bisect debug session IMHO... Yep, not that I'm an expert in this architecture but it's commonly used in multimedia device where realtime is often needed. Thanks -- Francis --
| Linus Torvalds | Linux 2.6.21 |
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Con Kolivas | Re: [PATCH][RSDL-mm 0/7] RSDL cpu scheduler for 2.6.21-rc3-mm2 |
| Andrew Morton | echo mem > /sys/power/state |
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) |
| David Miller | Re: [GIT]: Networking |
| Michael S. Tsirkin | Re: [RFC PATCH v2 03/19] vbus: add connection-client helper infrastructure |
