Nuutti,
That's a great answer to my concern.
I hope all prospective patch-submitters read your post.
:) brian
On Wed, Mar 17, 2004 at 05:49:19AM +0200, Nuutti Kotivuori wrote:
>
> I believe there's a bit of oranges and apples here - and definitely
> the "submit a patch" is a confusing comment and your woes are rightly
> placed here. I believe HACKING might require some clarification.
>
> The difference comes in the nature of the discussion.
>
> When some issue is discussed in the mailing list in general terms, the
> answers that contain the message "This is *so* low on my priority list
> that I don't even want to discuss it right now." are sometimes given
> with the comment "submit a patch".
>
> The proper response to that is "I am willing to code this feature by
> the guidelines in HACKING and iterate the patch into Subversion, and
> this is my proposed design, please give feedback on it."
>
> And I can guarantee people will discuss it then - if nothing else,
> then putting into words their reasons why it shouldn't be done - and
> possibly voting on it if it comes to that.
>
> So the actual message is not ever "if you come back with a patch,
> maybe I'll consider spending my time on it" - but it is "show your
> willingness to actually work this problem through its iterations, and
> I'll spend time commenting it."
>
> So, on the actual matter - SVNROOT patch - I think the first step
> would be to post a detailed proposal on how to handle the interface
> and get that approved.
>
> -- Naked
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 17 15:55:03 2004