Graeme.Winter at diamond.ac.uk
Graeme.Winter at diamond.ac.uk
Tue Jan 12 00:22:48 PST 2016
We worried about some of this with DIALS but went ahead with it anyway and it seems to have worked out OK – there has been some confusion where people get it a bit of a knot from time to time, but we have moved OK and are also moving to a more native GIT way of working – this is where the real benefit lies I think.
I would think for CCTBX the argument would be even stronger, as it’s needed all over the place (dials, ccp4, phenix, olex2…) and so having the flexibility offered by much easier and more reliable branching would be very useful. We’ve found that a handful of git commands will do what most ex-svn people need, with additional flexibility like partial commits.
Clearly we *could* make a git cctbx anyway and sync it to the cctbx svn, but that would seem messy and not really the right way to do things…
Does anyone else hold an opinion? In particular are there any known blockers to this?
Thanks & best wishes Graeme
From: cctbxbb-bounces at phenix-online.org [mailto:cctbxbb-bounces at phenix-online.org] On Behalf Of Luc Bourhis
Sent: 11 January 2016 16:45
To: cctbx mailing list
Subject: Re: [cctbxbb] Git
Can we revisit the idea of moving to git for cctbx?
This brings to mind a question I have been asking myself since the subject has been brought forth. The idea Paul wrote about on this list was a move to Github. I guess some, perhaps many, developers will keep interacting with the repository using subversion. I am worried this would clash with the workflow of those of us who would go the native git way. By that I mean creating many branches and merge points, which one would merge into the official repository when ready. I am worried the history would look very opaque for the subversion users. I would even probably create a fork on Github, making it even more opaque for a tool like subversion. Has anybody thought about such issues? My preferred solution would be for everybody to move to git but I don’t think that’s realistic. At the other end of the spectrum, there is putting in place a policy to keep the history linear.
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cctbxbb