Rafael Vanoni wrote: > Thanks Mark and Bill. > > 'hg log' outputs the entire revision history, and I didn't find another > way to get the revision from where the gate was created. > > 'hg parents' shows that tesla-gate is synced with 73, but that's because > Eric added a summary to the last commit. From the web page, cpupm-gate > is synced with 84 and powertop with 82.
Yes, cpupm-gate is synced with 84. changeset: 6051:e0718f7b2219 tag: tip parent: 5386:4fccf184d4a7 parent: 6050:b578f00bc056 user: Mark Haywood <Mark.Haywood at Sun.COM> date: Thu Mar 13 19:28:07 2008 -0400 summary: Sync with build 84. And powertop is synced with 82. parent: 5917:fe556dc3c14d user: Eric Saxe <eric.saxe at sun.com> date: Fri Feb 01 14:06:57 2008 -0800 summary: Merge with onnv_82 > Are those correct? > > thanks > Rafael > > > Mark Haywood wrote: >> Bill Holler wrote: >>> Mark Haywood wrote: >>>> Bill Holler wrote: >>>> >>>>> The "Mercurial way" would be to diff the repository with the earlier >>>>> revision of itself (the rev when it was cloned). ;-) Use "hg log" to >>>>> find the revision when the gate was created, and then use >>>>> "hg diff -r [REV]" to print the diff. >>>>> >>>>> The tesla gates I am aware of are cloned from OpenSolaris build 84. >>>>> Does OpenSolaris keep old versions of the gate? If so, you can >>>>> diff a tesla gate with build 84. >>>>> >>>>> Is there a webrev tool that works with hg? >>>>> >>>> Actually, webrev works with hg. At least the version on my build >>>> machine does. Bill's right that for the cpupm-gate you would need an >>>> onnv-b84 parent to use to generate the webrev. Assuming you had the >>>> two repos (onnv-b84 & cpupm-gate), then you should be able to create >>>> a webrev by setting two environmental variables, >>>> >>>> CODEMGR_WS: Workspace location (i.e., the path to the cpupm-gate repo) >>>> CODEMGR_PARENT: Parent workspace location (i.e., the path to the >>>> onnv-b84 repo) >>>> >>>> and then run webrev. >>>> >>>> Mark >>>> >>> Has webrev been updated to get the "active list" of changed file from >>> the repository's .hg directory? Or does the user have to supply >>> a file list? >> >> You don't have to supply a file list. I believe it uses hg-active to >> create the active list. I don't understand how hg-active works, but >> yeah it figures out which files have been modified. >> >>> Bill >>> >>> >>> >>>>> HTH, >>>>> Bill >>>>> >>>>> >>>>> Rafael Vanoni wrote: >>>>> >>>>>> Does anyone have a webrev for the tesla gate ? >>>>>> >>>>>> I'm just getting into it and could use the diffs from onnv, >>>>>> or a list of changes. >>>>>> >>>>>> thanks >>>>>> Rafael
