Greg KH <[email protected]> writes: > On Wed, May 19, 2010 at 10:22:58AM +0800, Roger WANG wrote: >> repo.meego.com is the output of our package build system (OBS), while >> git manages source code under development in upstream. When there is a >> new release in upstream, the source tarball is updated in OBS by the >> package maintainer, then a new version of package will be built. There >> is some native version control in OBS. > > s/native/naive/
Yeah, thanks for point out that. And we found the same here after some time. > > 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. Thanks -- Roger WANG, Intel Open Source Technology Center _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
