On Thu, Mar 25, 2004 at 08:05:05AM -0500, Jan Wieck wrote:
> The difference here is that instead of submitting a patch for review,
> which is then frozen, the branch owner can (and that means some will, no
> matter what your intentions are) keep modifying the branch during the
> review process, other than just keeping it in sync with conflicting
> changes to the trunk. How do you plan to prevent that?
I think it's much better for the reviewer to be able to see the history
of changes of the patch (branch), without having to look at the whole
patch again every time a small change is made to it.
Or do you diff two versions of a patch to see if the author only changed
what he says he changed? Wow, a diff of a diff, _that_ should be
difficult to read.
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Use it up, wear it out, make it do, or do without"
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
