James Hanley <jhanley@DGtlRift.com> writes:
> I had a question about patch submissions. I have an idea for a new
> feature, and I've implimented it as a "proof of concept," it is by no
> means production ready, but is more to get a conversation going as to
> the direction it should go before I put in too much effort. Should I
> post it to this list or to the dev? The faq says it should be the dev
> for fixing an issue or a new feature, but again this is by no means
> ready merging.
I thought I responded to this yesterday, not sure if you saw the
response or not (overeager spam filters?). Here it is again,
indented:
From: Karl Fogel <kfogel@red-bean.com>
To: James Hanley <jhanley@DGtlRift.com>
Cc: users@subversion.tigris.org
Subject: Re: Patch submission for new features
Date: Mon, 28 May 2007 19:04:37 -0700
References: <20070528211132.vb0g36iegosooc0o@sm.homelinux.com>
Message-ID: <87y7j8l70q.fsf@red-bean.com>
James Hanley <jhanley@DGtlRift.com> writes:
> I had a question about patch submissions. I have an idea for a new
> feature, and I've implemented it as a "proof of concept," it is by no
> means production ready, but is more to get a conversation going as to
> the direction it should go before I put in too much effort. Should I
> post it to this list or to the dev? The FAQ says it should be the dev
> for fixing an issue or a new feature, but again this feature is by no
> means ready for use. Can any patch be submitted to the dev list for
> peer review or clarification, etc?
dev@ is fine, using the guidelines in
http://subversion.tigris.org/hacking.html#patches
Best,
-Karl
--
Subversion support & consulting <> http://producingoss.com/consulting.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 31 01:52:32 2007