<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello Giuseppe<br>
<br>
Le 11/01/12 12:42, Giuseppe La Scaleia a écrit :<br>
<blockquote
cite="mid:CAAY8snCvWtVM3hUifL7REG0e_=JXYYZGUraHM_Ua8g7fQTUwEg@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
- We could also create a temporary clone on <a
moz-do-not-send="true" href="http://hg.geotoolkit.org/"
target="_blank">http://hg.geotoolkit.org/</a> where you
could push your changes (it would avoid the need to run "hg
serve" on your side). We would then incorporate those changes
in geotoolkit-pending with eventual edition (again the commits
would appear with your ID as if you pushed the changes
yourself). This is an approch close to the Linux development
model.<br>
</blockquote>
<div> </div>
<div>I prefer this option.<br>
</div>
</div>
</blockquote>
<br>
Fine, we will do. In Linux development (for what I have been told),
Linus creates a temporary clone where contributors push their
changes. Then Linux commiters pull those changes, review them and
push them to the main clone or ask for some modifications. After a
while the temporary clone is deleted (but every developper always
still have their changes on their own local copy, no matter if the
changes has been pushed to the main repository or not) and a new
clone is created for the next development cycle, and so one.<br>
<br>
I will ask to our administrator to create a
"geotoolkit-pending-20120111" clone and will let you know when it
will be done.<br>
<br>
Regards,<br>
<br>
Martin<br>
<br>
</body>
</html>