Comments on: The big patch theory http://blogs.igalia.com/vjaquez/2009/04/09/the-big-patch-theory/ words from a lazy coder Wed, 24 Feb 2010 07:28:49 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: linxe http://blogs.igalia.com/vjaquez/2009/04/09/the-big-patch-theory/comment-page-1/#comment-49 linxe Thu, 09 Apr 2009 20:27:25 +0000 http://blogs.igalia.com/vjaquez/2009/04/09/the-big-patch-theory/#comment-49 Yes, my old post I mentioned, refers to CodeStream, but think beyond the animation and cool electronic music. A patch is a mutation in the code (or genome), some times can be preserved, others simply is mutated or deleted and the selection isn't random. Yes, my old post I mentioned, refers to CodeStream, but think beyond the animation and cool electronic music. A patch is a mutation in the code (or genome), some times can be preserved, others simply is mutated or deleted and the selection isn’t random.

]]> By: amaneiro http://blogs.igalia.com/vjaquez/2009/04/09/the-big-patch-theory/comment-page-1/#comment-48 amaneiro Thu, 09 Apr 2009 17:47:19 +0000 http://blogs.igalia.com/vjaquez/2009/04/09/the-big-patch-theory/#comment-48 I *do* agree. In fact, I guess that "the commit is the atom of free software" (by commit I mean a patch approved). Great post! :D I *do* agree. In fact, I guess that “the commit is the atom of free software” (by commit I mean a patch approved).

Great post! :D

]]> By: vjaquez http://blogs.igalia.com/vjaquez/2009/04/09/the-big-patch-theory/comment-page-1/#comment-47 vjaquez Thu, 09 Apr 2009 17:36:01 +0000 http://blogs.igalia.com/vjaquez/2009/04/09/the-big-patch-theory/#comment-47 linxe, That's a very bold perspective. Intriguing at least. Have you seen this video? http://www.youtube.com/watch?v=f-LjU1xJ3gM It is done with the GStreamer commit information in it's git repository. You can see the project's collaboration as a living thing. linxe,

That’s a very bold perspective. Intriguing at least. Have you seen this video? http://www.youtube.com/watch?v=f-LjU1xJ3gM
It is done with the GStreamer commit information in it’s git repository. You can see the project’s collaboration as a living thing.

]]> By: linxe http://blogs.igalia.com/vjaquez/2009/04/09/the-big-patch-theory/comment-page-1/#comment-46 linxe Thu, 09 Apr 2009 17:00:35 +0000 http://blogs.igalia.com/vjaquez/2009/04/09/the-big-patch-theory/#comment-46 "... the patch must be small and specific enough to survive several changes in the base code, and could be applied cleanly even if the surrounding code had changed since it was created." Wow that's natural selection (in a Darwin's sense)! Some time ago I posted about graphical "evolution" of programs, now I understand some points why the code changes in peculiar ways. "A patch must be small enough to be easily understandable, attack a single issue, self-contained (in must have all it needs to solve an issue), well documented, complete, honour the project code-style, and so on." I must think a little more, but probably you can study a "source code" and its evolution using molecular clocks approaches. “… the patch must be small and specific enough to survive several changes in the base code, and could be applied cleanly even if the surrounding code had changed since it was created.”

Wow that’s natural selection (in a Darwin’s sense)! Some time ago I posted about graphical “evolution” of programs, now I understand some points why the code changes in peculiar ways.

“A patch must be small enough to be easily understandable, attack a single issue, self-contained (in must have all it needs to solve an issue), well documented, complete, honour the project code-style, and so on.”

I must think a little more, but probably you can study a “source code” and its evolution using molecular clocks approaches.

]]>