On Wed, 2008-04-09 at 11:46 +0200, David Nielsen wrote: > That way you'll do (example): > > f8 | f9 > ----------------- > -1.fc8 < -1.fc9 (Initial build of same package on branch and > trunk) > -1.fc8.1 < -1.fc9 (Made a change on branch) > -1.fc8.1 < -2.fc9 (Imported new trunk) > -2.fc8 < -2.fc9 (Merged the trunk into branch) > -2.fc8.1 < -2.fc9 (And do another branch change) > > Without breaking upgrade path at any point in time. > > That would work yes, but you know what would also work.. CVS, dead in > a ditch, it simply should not be able to create the kind of > inconsistency it did for me, that was clearly a CVS bug. I have not > worked with CVS before starting as a Fedora contributor, the fact that > following the guide to the letter can occasionally cause CVS errors > like what I got (it appeared to not transfer the files completely but > I was not allowed to check the files back in - the quick fix was > merely to bump the build) - well it does tend to frighten me. Excuse me? CVS? What does a version control system have to do with this? You might mean that commit hooks would not allow you to do so, but bear in mind that they currently have no idea what builds are currently done and it's probably best that way. -- Lubomir Kundrak (Red Hat Security Response Team) -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
