Patrick Mayweg <mayweg@qint.de> writes:
> > Patrick, I don't want to stand in the way of work getting done, but
> > should point out that your commit access is for the Java bindings.
> > The limitation is not because anyone thinks badly of your coding, just
> > that we hadn't seen enough patches from you to say "Give this guy full
> > commit access" :-).
>
> I am sorry that you feal that way. I have posted the modifications
> twice to the mail list. But nobody cared to answer. This patch is
> needed to configure the java-bindings.
Uh, that restriction is not "how I feel", Patrick, it's how we work.
I'm just the messenger here. The fact that your post didn't get a
response doesn't mean that someone approved the commit -- if someone
consciously approved it, they'd take the ten seconds to say so! No,
it just means that no one had time to review it.
In this case, the best solution is pretty simple, though -- next time,
your log message should say "This patch is needed to configure the
java bindings." Then people would have known that it was part of Java
bindings maintenance.
I see that you and Justin are discussing what to do, so the technical
questions will get sorted out one way or the other.
My only request is that if you make a commit that's not obviously
about Java bindings, then please say in the log message how it relates
to the bindings, so people don't need to wonder if you're suddenly
committing all over the codebase for non-Java issues (in other words,
a change in the type of your commit access, for which we have a
process -- and, by the way, good reasons for that process).
Thanks,
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 12 17:36:41 2003