[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index


From: Andy Whitcroft <apw_at_shadowen.org>
Date: 2004-07-19 18:00:18 CEST

--On 19 July 2004 09:10 -0500 kfogel@collab.net wrote:

> Andy Whitcroft <apw@shadowen.org> writes:
>> It seems that there is little advice as to the route for a non-commiter
>> when wishing to propose a revision or issue be ported to a branch.
>> It makes sense to use the dev@ list and a similar process to [PATCH];
>> something like [PROPOSAL]. Below is a first take at documenting
>> this method.
> Do we really need to document this? Everything else about the project
> says to mail users@ or dev@ (and if someone mails users@ with
> something that really belongs on dev@, they usually get steered to
> dev@ pretty quickly).

Hmmm. Well I wasn't sure. Patch submission seems to be documented in this
way so it seems consistent. But realistically its your call. Most
proposals are going to come from the committer community anyhow. So
perhaps not.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 19 17:59:49 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.