> you don't. no delta contains the entire source for a release or even all > the patches since the last one. nor is the delta that updates the version > strings necessarily the last delta that went in before tagging. > > you need to look at the cvs tag. there's no other answer.
Okay, okay.. cvs20hg reads in the RCS files and tries to infer which files were committed at about the same time. It then dumps a whole bunch of file changes in a changeset in mercurial. It does this only on one branch at a time. So this is what I get in my mercurial repository: changeset: 4851:af8525c24fc4 tag: tip user: shadow date: Thu May 10 00:15:57 2007 +0000 summary: DELTA vos-namelen-for-dump-restore-is-stupid-20070509 changeset: 4850:46f7d864babf user: rra date: Tue May 08 22:49:44 2007 +0000 summary: DELTA ka-forwarder-licensing-20070508 changeset: 4849:853dcded1b5b user: rra date: Mon May 07 19:16:02 2007 +0000 summary: DELTA quickstart-pam-docs-20070507 changeset: 4848:968f233d7859 user: rra date: Mon May 07 17:17:42 2007 +0000 summary: DELTA up-preserve-dir-mtime-20070507 What I want to know is which of the these mercurial revisions (which most all of match up with a delta), will be equivalent to the Openafs_1_5_18 tag _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
