p.s. and of course the "headaches" are a tradeoff with some advantages
On Mon, Aug 6, 2012 at 6:19 PM, Barak Raveh barak.raveh@gmail.com wrote:
> I am cool with moving to git too. I played with it a little ever since > Daniel's demo. It does come with some "headaches" that are avoided in svn > (instead of just committing - first stage, then commit locally, then push). > But it will probably be fine with everybody after some getting used to. > > > On Mon, Aug 6, 2012 at 6:17 PM, Dina Schneidman duhovka@gmail.com wrote: > >> I think it is a good idea if we all use the same repository to >> eliminate the need to sync svn and git. >> I am sure we can all easily learn git basics fast. >> >> On Mon, Aug 6, 2012 at 6:11 PM, Ben Webb ben@salilab.org wrote: >> > On 8/6/12 1:54 PM, Barak Raveh wrote: >> >> >> >> About git - it's kinda in the twilight zone now, Daniel already has set >> >> a git repository that he keeps in sync with the svn every once in a >> >> while, but it might take a little while until we leave svn, probably >> >> only following the next release? Daniel? Ben? >> > >> > >> > When we last discussed this, the tentative plan was to move to git >> after the >> > next stable IMP release. If people have strong opinions either way about >> > this, now would be the time to say so! (If you have no experience with >> git >> > but are interested in playing with it, you could try out git-svn, which >> > works quite nicely as a 'frontend' to IMP's current SVN repository.) >> > >> > Ben >> > -- >> > ben@salilab.org http://salilab.org/~ben/ >> > "It is a capital mistake to theorize before one has data." >> > - Sir Arthur Conan Doyle >> > >> > _______________________________________________ >> > IMP-dev mailing list >> > IMP-dev@salilab.org >> > https://salilab.org/mailman/listinfo/imp-dev >> _______________________________________________ >> IMP-dev mailing list >> IMP-dev@salilab.org >> https://salilab.org/mailman/listinfo/imp-dev >> > > > > -- > Barak >