[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] What is our policy on patches?
|
Hey all,
One way to resolve this would be to take a look at CVS log mail support
again. Now that I'm a SourceForge project admin, I've learned how to set
this up for a CVS repository. We could get the commit logs for selected
projects to be sent to a mailing list, e.g. cdt-cvs. We would then
reserve the cdt-patch list for non-committers to request patches or to
invoke voting on certain patches.
If we get a consensus, I'll volunteer to try and get this going (assuming
the eclipse.org folks let us).
Thoughts?
Doug Schaefer, Senior Software Developer
IBM Rational Software, Ottawa, Ontario, Canada
John Camelon/Ottawa/IBM@IBMCA
Sent by: cdt-dev-admin@xxxxxxxxxxx
09/15/2003 08:55 AM
Please respond to
cdt-dev@xxxxxxxxxxx
To
cdt-dev@xxxxxxxxxxx
cc
Subject
Re: [cdt-dev] What is our policy on patches?
> Many now, consider the mailing list patch as "spam".
+1
I guess my main point is that if we were voting on patches or debating
the content of these patches prior to them being committed, then the
content on the list is useful. If we are not doing that, then it
merely serves as a reminder to do a CVS update.
JohnC
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev
