On Sat, Apr 09, 2005 at 11:36:27AM -0400, Alan Stern wrote: > Greg: > > When you work on accepting and merging patches, do you use a single tree > for all the changes or do you have separate trees for usb, pci, i2c, and > so on? If you use a single tree then there's no real choice but to export > all the patches together -- cherry-picking the subsets will inevitably > lead to inconsistencies.
True, it already has. I try to use just 1 tree, but there interdependancies at times. > On the other hand, if you really do keep the different areas separate > while working on them (which would force Andrew Morton to do the necessary > reconciliation, right?) then the patches you export also need to be kept > totally separate. Having a single "series" file might work but it > wouldn't be a good idea. It isn't a good idea from the "testing in -mm" idea. Lots of times, it really helps to know that backing out the driver core, or the usb patches, fixes an issue. That helps narrow down the scope of things when I am carrying 400+ patches around at once. <nice fancy idea snipped> > What do you think? I think that I don't have the time to write such a system, but if someone else wants to do it for me... :) Anyway, let's see how we are going to work with git, that will throw something else into the system. thanks, greg k-h ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
