Re: Commit signing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Mon, 15 Jan 2007, Shawn O. Pearce wrote:

> I've never met anyone on this mailing list in person, but the quality 
> (or lack thereof sometimes) is evident in my work, and since its all 
> peer-reviewed anyway Junio finds little risk in incorporating the good 
> stuff into git.git.  No certificate required.

Exactly. I think it is one of the reasons monotone is so unpopular (at 
least as far as I am concerned): it makes the start really cumbersome. And 
in the end you gain nothing.

And you see what the result is when looking into corporate projects. More 
often than not, bureaucratic procedures (e.g. tracking time, meetings, 
specifications) supersede quality-assuring procedures (e.g. permanent 
updates on the TODO list, code review, discussion on implementation 
details), and quite often, the code just sucks.

My favourite example is when I found 34 different (!) implementations of a 
tree structure in the same project.

So, if you start relying on the validity of code just because somebody 
signed it, you will reap trouble.

Ciao,
Dscho

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]