Some of you have mentioned that you have waited so long for a patch to
get committed that it breaks when you try to apply it to the latest.
The way I have dealt with that in the past for patches I am trying to
commit is to do an svn update -r <revision> , where <revision> is the
revision specified in the patch file (at the header for each file change).
Then I apply the patch, and do "svn update" and it often updates without
conflicts; if there are conflicts theyr'e generally easy to resolve. If
they aren't, *then* you can ask the contributor to re-do their patch.
That way the poor contributor doesn't have to keep rebuilding their
patch file...
David
begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard
