Re: [mdt-papyrus.dev] Git/SVN (was Re: Problem with loading custom Prope

[GERARD Sebastien 166342 <Sebastien.GERARD@xxxxxx>]

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

 

www.eclipse.org/papyrus

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian W. Damus
Envoyé : mardi 12 mars 2013 14:03
À : Papyrus Project list
Objet : [mdt-papyrus.dev] Git/SVN (was Re: Problem with loading custom Properties View context models)

 

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?

 

cW

 

 

On 2013-03-12, at 8:17 AM, Tom Morris <tfmorris@xxxxxxxxx> wrote:

On Tue, Mar 12, 2013 at 7:00 AM, <give.a.damus@xxxxxxxxx> wrote:

  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.

 

Tom

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev