"Matthew Persico" <[EMAIL PROTECTED]> writes: > "Wim Kerkhoff" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED]... > > > What most people suggest to develop on the mainline. Fixes for past > > releases, expiremental development, and so on are done on branches, then > > merged back to the mainline as appropriate. > > But what if I have released 1.7, commited 1.8 and 1.9 but not released them > and need to fix 1.7. Can I create 1.7.1.1 if 1.8 exists?
Yes. The best policy is to create a branch tag (tag -b) for each release, just in case you need to go back and patch it. If you have a plain tag, you can create a branch tag with tag -b -rplain_tag branch_tag If you have no tag for the release, you'll have to use dates, or somehow figure out the revision number for each file, and branch tag them individually. -- -- Stephe _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
