Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Elisa Cargnel wrote: > And I need to commit a version after revision 1.2, But I wouldn't like to make a branch. > I'd like to have the revision 1.3, this depends on how my files are organized. You can't, because someone has already checked in a revision 2.1. It is impossible to go backwards in time, so the next revision will be 2.2 (or higher if you force it, which isn't recommended). > I saw in old topics that this was a problem on resurrecting files. Now this is solved for resurrection. > Would it be possible to have in committing files too or you think this is a bad behavior? It's just impossible to do (as it doesn't make sense). Revision numbers should bever be taken as anything but a unique way of identifying a revision.. reading anything magic into them is doomed to failure. (commit -r is going away very soon unless there is an overriding reason to keep it, and I can't think of any at all right now). Tony