Are you uploading one diff for each separate change to a review request, or
are you uploading diffs containing just the new changes requested for each
iteration?
The idea is that one review request maps to one diff. Each diff you upload
is just another iteration on that diff, but one that consists
Sorry if the word "baseline" is confusing--now it seems like it's the
wrong word to use.
What I mean is that I'd like to see the cumulative effect of all
diffs, because as I mentioned in the example workflow, it's necessary
and important at the end of the iterations to ignore the intermediate
dif
It sounds like he means the perforce baseline concept... meaning the
youngest common ancestor node in the revision tree
Jeff
O|||O
Help me and the Leukemia and Lymphoma society fight blood cancers:
http://pages.teamintraining.org/dm/tucson08/jandros
On Thu, Nov 6, 2008 at 1:17 PM, Christian
I'm confused as to what the problem is. When you say baseline, you mean
what's in the repository? Just use the "Jump to revision" for that. Clicking
"View Diff" will take you to the most recent diff, which compares against
what's in the repository.
If that's not what you mean, can you explain your
Hi all. I feel it's pretty essential to compare updated diffs with
baseline, but I can't find any mentioning of it in this group or the
bug tracker.
What I mean is this: suppose you have two diffs in a review request.
Right now you'll see this in the diff view:
Jump to revision: 1 2
Changes betw
