I was checking the tags to see if DisplayResOSX.cpp bug fixes were in (they are, thanks), and was wondering about the philosophy of branching vs tagging. In the case of this file, r1.6 is the same as r1.4.2.1, which isn't a problem, but does sort of "clutter" the repository a bit.
The "best" way is probably whatever is easiest for you, but I assume you do it through locking explicit revisions in your local copy, applying patches, and then checking in?
-- Nigel Pearson, [EMAIL PROTECTED] | "People say I'm strange, does it Telstra BI&D, Sydney, Australia | make me a stranger? Office: 8255 4222 Fax: 8255 3153 | My best friend was born Mobile: 0408 664435 Home: 9792 6998 | in a manger" -DC Talk
_______________________________________________ mythtv-dev mailing list mythtv-dev@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
