> I can understand part of the reason for this... 4.0-RELEASE is right
> arround the corner, and people are focusing on delivering a stable product,
> not introducing alpha code into the system at the last second. the current
> rpc.lockd is a known value, placing a "maybe" version into the stream at
> this point would do no one any good.
OK, that seems a fair and reasonable assessment.
> Mmmm.... feedback would be very good. Also, what are the chanches of
> getting the 3 required functions MFC-ed? fh{open|stat|statfs} ?
I'd say that's no problem - with 3.5 still a few months away, now's
the best time for that.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message