Mark D. Baushke wrote:
| Therefore, I suppose that there could be a need for .origin to be
| the first revision on TRUNK
This would seldom mean much across multiple files, so I still think
.origin should not be used. The case Frank cited, where he is
basically trying to diff against an import (thought not generated
using the import command), is the only one where all the .origin
revisions will be related in a sensible way, and even then only if no
files have been added or removed on the trunk. Once files have been
added or removed, you degenerate to the case where the .origin
revisions (or even 1.1 revisions) of these files could have been added
at different times and offering to calculate .origin is misleading at
best.
The only consistent way to do this is to tag everything after the
"import" and diff against that tag. This tag couldn't even really be
automated, except in something like the import command, which imports
a set of files at once and tags the set.
.origin makes no sense.