Danek Duvall writes: > A compromise could be something like this: > > -r r1 changes from p(r1) to r1 > -r r1: changes from p(r1) to WD > -r r1:r2 changes from p(r1) to r2
I don't see that as a compromise, because, unlike the second case, it still has the expensive (and possibly un-do-able) p() function in it. It's not WD that's necessarily attractive to me (I can do a commit if that's what's needed); it's the fixed local (fast!) starting point for the diff. Could we have an option or mechanism that avoids taking the p() of anything? The reason I'd want to have any sort of option here is to be able to generate a webrev from a known point in time without having to bother with any known parent -- and likely in a case where I have no access to any parent (because the network is down or too expensive to reach). As for how I know which revision to give to this option, that's my problem. ;-} If it's not obvious by looking at hg history, then I shouldn't be doing this. -- James Carlson, Solaris Networking <james.d.carl...@sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
