On Wed, May 19, 2010 at 12:39:48PM +0800, Roger WANG wrote: > Greg KH <[email protected]> writes: > > > 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, > > What's "tree of quilt patches"? Does it mean generating patches from > branches against upstream branch, or manage the patch files themselves in git?
Manage the patch files themselves in git, just like you all are currently doing with your kernel git package. You really don't want to expand the patches out into an original tree, it's a pain when rebasing with upstream, and can cause big problems as sometimes all you really want to do is drop patch 43 of a 100 patch patchset. With an expanded tree, that's pretty difficult. good luck, greg k-h _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
