On Fri, 11 Sep 2009 03:22 -0000, des wrote:
"Jason J. Hellenthal" <jas...@dataix.net> writes:
If I may, I would like to introduce a distributed targeting system to
this conversation in addition to crashinfo. Given with the above
conversations I cant help but think that in a case like this it would
be helpful to setup a central database for collection of information
and write a little bit more code into crashinfo for uuencoding a blob
to send through email or maybe another way so data can be collected,
sorted & analyzed with statistics spilled out into a web page for
review.
It's a good idea in principle, but I'm worried that such a system might
get flooded with crash reports from people running old -STABLE versions
and / or local patches. There is no way we can control that, neither in
the client script nor at the receiving end.
DES
I am thinking more of something like the distributed.net project where as they
have two very well defined projects or areas that they can allow their users to
work on and that they can close at any point in time. This would certainly get
rid of the unwanted branch reports.
As for the others I can only help but think of Subversion, uuids, md5 sums, and
specific version strings that are made up on compile time so as if r??????M is a
version that is being submitted it would be turned down by the waiting server
or stopped directly on client side. And for the rest of the world running CVS ;)
I don't have something coming to mind at the moment.
I am pretty sure though by any means that a solution to all the above can be met
with prejudice.
--
Jason J. Hellenthal
http://www.DataIX.net/
jas...@dataix.net
0x691411AC
- (2^(N-1))
_______________________________________________
svn-src-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
