[scm-migration-dev] Incremental webrev

2008-04-01 Thread Richard Lowe
Mike Kupfer writes: >> "Rich" == Richard Lowe writes: > > Rich> However, at present, it outright doesn't work (errors from Hg, > Rich> because the parent (webrev) isn't a workspace). > > I don't understand. If you're using -p , it should > be -p . It can be either, dp's reworking of webr

[scm-migration-dev] Incremental webrev

2008-04-01 Thread James Carlson
Mike Kupfer writes: > > "Rich" == Richard Lowe writes: > > Rich> However, at present, it outright doesn't work (errors from Hg, > Rich> because the parent (webrev) isn't a workspace). > > I don't understand. If you're using -p , it should > be -p . webrev(1) documents otherwise: INCREME

[scm-migration-dev] Incremental webrev

2008-04-01 Thread Mike Kupfer
> "Rich" == Richard Lowe writes: Rich> However, at present, it outright doesn't work (errors from Hg, Rich> because the parent (webrev) isn't a workspace). I don't understand. If you're using -p , it should be -p . mike

[scm-migration-dev] Incremental webrev

2008-03-30 Thread Richard Lowe
webrev -p is pretty much not possible to support reliably over Hg (for the same reason it's not entirely foolproof with TW). However, at present, it outright doesn't work (errors from Hg, because the parent (webrev) isn't a workspace). Could we teach webrev to fall back to the unknown SCM logic