"Masterson, David" wrote:
> How about:
>
> cleartool lsvtree -short <file> | xargs -lt cleartool describe
>
> Add options of your choice (like -fmt on describe). Obviously, this is a
> little more difficult to do on NT, but it shouldn't be hard to whip up a
> Perl script to do it.
>
David Hallman wrote:
> Wouldn't the annotate command do this (cleartool man annotate)?
David & David,
to begin with, cleartool lsvtree -short does not give you all versions of an
element. Somewhat better would be
cleartool lsvtree -all -nco <file> | cut -f -d' ' | grep ... | xargs -l -t
cleartool describe
But if we use -all, we have to eleminate branch names and .../0 versions. And
you cannot start at a specific version - lsvtree ignores any version extension.
Let me try to get it across again: When you have a particular version (not
necessarily /main/LATEST), we want to know the history of exactly this version,
i.e. all the checkin comments of deltas contributing to this version, i.e. its
linear predecessors and the versions on those branches that were merged into
this linear sequence of branches - but not including that of any existing
sibling versions, or versions on dead end branches that never made it into
main.
Or, in other words: think of the checkin comments being written into the file,
and then imagine a diff between these comment sections of a version and one of
its predecessors - this would be the true change history (as expressed by
checkin comments) of a version, back to that other version.
And (as we, at our site, have to document all the changes between some baseline
and the previous) we want to exclude versions preceding some other specific
version (but not by date - think of a branch being started and worked upon
before some version on main was promoted to "released in baseline N"; probably
we're not the only ones to begin work on baseline N+1 before baseline N is
shipped).
I had looked into cleartool annotate, and it almost might have been a viable
solution (using -ndata). But what would be missing from an annotate output is
all that happened on branches that were merged into what man annotate calls
"line of descent". (Repeat the collected checkin comments when doing the
checkin after the merge? Trust the practitioners to be good? Write a tool that
does this?)
Regards,
-Wolfgang
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:22:25 EDT