On Wed, May 19, 2010 at 10:43:55AM +0800, Roger WANG wrote: > > Please _never_ depend on the version control in OBS as a substitute for > > any real version control (backups, changes, merges, branches, etc.) To > > do otherwise is to loose lots of data. > > > > Besides development happening as much as possible in upstream, is there > any best practise (for OBS) to manage large amounts of distro patches? > Somewhere quilt is used for kernel patches.
quit is used to manage patches, not to store them in a source code control tool. At Novell, we use git to manage a tree of quilt patches for our kernel, just like you do for MeeGo's kernel. I've been doing the same thing for upstream kernel development for many years now just fine, handling 5-700 patches a kernel release with no problem. What's wrong with git for handling your patches? And why would you want lots of distro patches? :) thanks, greg k-h _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
