<br><font size=2 face="sans-serif">So let go with r311.</font>
<br><font size=2 face="sans-serif">Thanks. Thipadin.</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Ashley Pittman <ashley@pittman.co.uk></b></font>
<p><font size=1 face="sans-serif">11/04/2009 02:01 PM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> Pour : thipadin.seng-long@bull.net</font>
<br><font size=1 face="sans-serif"> cc : florence.vallee@bull.net, francois.wellenreiter@bull.net, padb-devel@pittman.org.uk, Sylvain.JEAUGEY@bull.net</font>
<br><font size=1 face="sans-serif"> Objet : Re: Réf. : Re: Réf. : Re: [padb-devel] Patch for Support of PBS Pro resource manager</font></table>
<br>
<br><font size=2 face="Courier New">On Wed, 2009-11-04 at 13:31 +0100, thipadin.seng-long@bull.net wrote:<br>
> <br>
> As I can get it, you propose me two things: <br>
> 1-start from r311 <br>
> 2-create branch with stable state for a while (must provide a google<br>
> login)and merge branch later. <br>
> So what's the best thing for you ? For me I don't need access to<br>
> commit, just check out is enough. <br>
> And I don't want to hold parallel version any longer, just want to get<br>
> to common version quickly. <br>
<br>
You could either work against the head which shouldn't be getting<br>
commits which would conflict with your work or you could work against<br>
r311, I'll be happy with either. You can checkout r311 using the<br>
following command if you need to.<br>
<br>
$ svn co -r 311 https://padb.googlecode.com/svn/trunk padb<br>
<br>
Looking over your patch it should all be straightforward other than the<br>
server part, does PBS often have two active servers on the same machine?<br>
What might a list of active jobs look like in this case?<br>
<br>
Ashley<br>
<br>
-- <br>
<br>
Ashley Pittman, Bath, UK.<br>
<br>
Padb - A parallel job inspection tool for cluster computing<br>
http://padb.pittman.org.uk<br>
<br>
</font>
<br>
<br>