"Files" <files@poetryunlimited.com> writes:
> In light of the recent events, I were to ask Patrick to update a
> segment of the Mandrake RPM build set that is directly impacted by and
> depends on his javahl update which he just recently put in, is there
> an issue to asking Patrick to making this update? Or should it go
> through someone else?
It's normal for a bindings maintainer to update other areas (such as
the build system) that are affected by bindings changes. This can
include OS-specific packaging glue, if the bindings committer feels
comfortable making the change there.
> Patrick's concern was that since he has access rights on the java
> bindings area, he did not want to impose on the maintainer of the
> Mandrake RPMs.
>
> Understandable and laudable. I commend him for his discretion.
>
> However, since I was the last maintainer of the Mandrake RPMs, but no
> longer have commit rights, does that mean that ownership of the
> Mandrake RPM build set reverts to the previous owner or is it still
> under my care, with help from the list, or what?
It's under the care of the other committers, with help from you.
> Any clafirications on the matter would be greatly helpful.
If Patrick has any concerns about the patch, it would be best if you
guys could post it (especially considering Mike's generous review
offer). If it's just a matter of worrying about formal process, then
I think Patrick can go ahead and do what he feels is right.
> In the meantime, I will post the patch I had felt belonged as part of
> the javahl update, as a general patch, with the request that someone
> review my notes and then apply it for me.
Sounds great! Thanks,
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 29 19:07:56 2003