Thats a pretty simple conflict resolution.
I think trying to lock down code while issues are in progress is
generally not a great idea. More cons than pros in my mind. Generally,
the onus is on the patch writer to continue to resolve conflicts until
they commit AFAICT.
That said, I have no p
Hrm, my work for LUCENE-1713 conflicted... I already added this to the
renamed class.
Please do not commit any changes to Range* classes before LUCENE-1713 is
resolved.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Mes
