<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Il 02/10/2012 22:45, Filippo Spiga ha
scritto:<br>
</div>
<blockquote
cite="mid:96C84FAA-97FE-40A8-9C23-D2E82CF55E14@gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
Dear Stefano,
<div><br>
</div>
<div>as you an many others already know, I am involved in the GPU
porting of QE, together with Ivan Girotto (ICTP) and hopefully
two new people based in US. The QE-GPU code is on QE-FORGE ( <a
moz-do-not-send="true"
href="http://qe-forge.org/gf/project/q-e-gpu/">http://qe-forge.org/gf/project/q-e-gpu/</a> )
and it is still a work in progress (if you want to contribute,
drop me an email!). It works as a plugin for QE so basically it
is (almost) aligned with the current official release and/or the
current SVN version. We have a stable release, aligned with QE
5.0.1 but I am working now on new features on new packages. I am
also broadly involved in other stuff around the main
distribution.</div>
<div><br>
</div>
<div>I catch the opportunity to spend few words about the
versioning system. I do like the GIT philosophy, the fact that
it is light and distributed and fast. But I also believe that it
is a pain. I tried it. GIT is not the solution, GIT is a tool
like SVN or CVS. Actually we can efficiently use SVN by simply
follow a basic rule: work on an update local copy. I do not
understand why people do not do "svn update" every time they
start to coding. I do that. All the time. We have to say
honestly that merging two versions of the code that are
temporally distant is a pain whatever versioning tool is used.
So before start any discussion about change what we have (a
change is not the solution) is much better to work to change our
habits and always have in mind that we are not alone but there
is a wide community that makes new developments and changes on
the code every day. That's my opinion as computer scientist who
works with non-computer scientists (and lot of them are much
much more capable than me).</div>
<div><br>
</div>
</blockquote>
<br>
<br>
I completely agree with Filippo, <br>
and I would like to suggest just another useful (at least to me)
habit,<br>
before doing "svn update" (every day!) do an "svn diff -r HEAD"
between local version and the trunk<br>
just to see if there are any possible non detectable conflicts (two
guys working on the same<br>
file but on different lines ) that may break-up the development you
are doing.<br>
This will, keep you development version up-to-date and working (or
not working) properly. <br>
Time to time someone may add a bug to your local version too, <br>
but, usually, this will not last longer, and I think it is a good
collaborative practice if<br>
you do not wait someone else to fix the bug, and help the developer
introducing the bug to solve it,<br>
<br>
carlo<br>
<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
Ph.D. Carlo Cavazzoni
SuperComputing Applications and Innovation Department
CINECA - Via Magnanelli 6/3, 40033 Casalecchio di Reno (Bologna)
Tel: +39 051 6171411 Fax: +39 051 6132198
<a class="moz-txt-link-abbreviated" href="http://www.cineca.it">www.cineca.it</a></pre>
</body>
</html>