| Thanks Sébastien. That's good news! I can certainly wait until the summer. But, I'll nonetheless see whether it's an easy transition. I'd be inclined to try it after next week's M6. Until then, I can't afford a hiccup in the current process. :-)
cW
Alain Leguennec from Esterelle Technolohies is working like that. BTW, Papyrus is going to switch to git in this summer. Best, Séb. ------------------------------------------------------------------------------------------------------------------------------------------------ Sébastien Gérard +33 (0)1 69 08 58 24 / +33(0)6 88 20 00 47 CEA Saclay Nano-INNOV Institut CARNOT CEA LIST DILS/Laboratoire d’Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE), Point Courrier n°174 91 191 Gif sur Yvette CEDEX Hi, Tom, Thanks for the tip. I certainly would prefer a git repository; I'll have to read up on this. What does the Papyrus team think of committers working in this mode? Is it endorsed? Do any current Papyrus committers work this way?
And no, probably there is no "svn bisect" because in git it depends on having the entire history stored locally for very quickly switching the workspace between commits (analogue of revisions). Something SVN cannot hope to do.
You could always use git2svn/git svn and do the bisect in git. Some people prefer a local git-based solution even if the official repository uses svn. _______________________________________________ mdt-papyrus.dev mailing list mdt-papyrus.dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
|
