>>>>> "DBP" == Daniel B Price <[EMAIL PROTECTED]> writes:
>> No. Alternate arrangements would need to be made in that case to get
>> the
DBP> (Sorry for the awful formatting-- the mailing lists are eating posts
DBP> on me again, so I never got this in email).
DBP> Matt-- nothing would preclude us from doing as Dean asks, though,
DBP> right? I do like the idea of interested parties being able to apply
DBP> those suggested diffs. It is a common practice in other communities.
No -- webrev could be taught to generate yet another form of diff. Or maybe it
just includes a link to a tarball containing unified diffs for everything in
the webrev. You'd still end up with the workspace synchronization problem,
which may or may not be an issue, depending on the area changed.
Honestly, though, if this ever became more than the rarest of cases, I'd treat
it as a sign that something's broken with our process. Reviewer time is too
valuable to waste it on getting workspaces exactly in sync, applying patches,
doing builds, and so forth. If the reviewer wants to play with bits, they
should get a binary or archives.
DBP> I'll happily sponsor anyone who wants to work on this change to
DBP> webrev. We also need to make webrev emit pointers to
DBP> http://bugs.opensolaris.org.
Would it generate OS pointers in addition to monaco ones? I really don't want
to have to choose. Is there some JavaScript magic that could be worked here
(and no, I don't want to hear from the JavaScript-is-evil crowd)? Maybe links
point to OS only if the JavaScript can't resolve monaco's hostname.
Matt
--
Matt Simmons - [EMAIL PROTECTED] | Solaris Kernel - New York
Man does not live by words alone, despite the fact that sometimes he has
to eat them. --Adlai Stevenson
_______________________________________________
opensolaris-discuss mailing list
[email protected]
