|
|
Blitz Devel : |
From: Todd Veldhuizen (tveldhui_at_[hidden])
Date: 2002-10-08 15:15:44
Theodore Papadopoulo wrote:
> More generally, what are the rules for comitting.
> Should we send the patch first on the mailing list
> to get comments and or approval... In essence, how
> do we synchronize ??
Let's see, I'm not sure what the process for committing updates should
be either. How about if you mail your patch to blitz-dev and say "I am
going to commit this tomorrow unless someone objects."
I'd suggest we do this with any patch where we're not confident of the
technical issues, or if there is a possibility the patch will be
controversial. Straightforward patches I think can just be committed
without debate (btw add yourself to blitz-cvs if you want to get the
syncmail notices about cvs commits:
http://lists.sourceforge.net/lists/listinfo/blitz-cvs).
Does this sound like a reasonable process? Eventually we can start
using the "submit patches" interface on sourceforge, but I think that's
primarily geared toward untrusted users without cvs write access. If I'd
done this the other day with my testsuite/chris-jeffery-3.cpp "patch"
then Julian could have pointed out it was Koenig lookup problem before
I committed. :)
Also, does anyone know if there is a way to get blitz-dev and
blitz-bugs emails fed directly into the sourceforge tracking
system?
Cheers,
Todd
-- Todd Veldhuizen / tveldhui_at_[hidden] / Indiana University Computer Science _______________________________________________ Blitz-dev mailing list Blitz-dev_at_[hidden] http://www.oonumerics.org/mailman/listinfo.cgi/blitz-dev