<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>El 04/07/2011, a las 6:43a.m., Mariano Martinez Peck escribió:</div><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin-top: 0pt; margin-right: 0pt; margin-bottom: 0pt; margin-left: 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex; position: static; z-index: auto; "><font class="Apple-style-span" color="#000000"><br></font>
Esteban proposed to create a branch for to track svn sources<br>
separately, while blessed repository will be used as a public source<br>
of VMs we building/using.<br>
If everyone agrees with such setup, then i can do the changes.<br></blockquote><div><br>+9999999<br> <br>That makes completely sense for me. It would be great to have a specific clone for tracking SVN and let blessed as the official/working clone. <br>
I would LOVE if blessed could always working and in zync with ConfigurationOfCog. So that you never need to worry. Always the same procedure. <br>And would like also that blessed is the one used for Hudson. Because, as I say, that is the way that people expect to build the VM, so we can easily detect when there is a problem. <br>
<br>Sorry for just giving my thoughts without actually do them. But this is what I can do at the moment.<br><br></div></div><br></blockquote><div><br></div></div>+1 (of course, that was my proposal ;) </body></html>