| Re: [mdt-papyrus.dev] Migration to Git |
|
Hi Alain, hi all, We used the Eclipse procedure to migrate from SVN to Git, so we actually barely did anything ourselves. I thought the SVN revision number would
be available in the GIT history, but it seems that it’s not the case. Regarding the SVN repository, it will probably not remain forever. It should be available in read-only mode until the Eclipse SVN support is stopped
(At the end of the year I guess). I think you can obtain a zipped copy of the repository afterwards. Regards, __________________________ Camille Letavernier +33 (0)1 69 08 00 59 -
camille.letavernier@xxxxxx CEA LIST - Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE) Papyrus :
http://www.eclipse.org/papyrus De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Alain Le Guennec Hello Camille, hello all, I have a couple of questions relative to the migration to Git: -Once the svn repository is made readonly, what will be its retention policy? Can we assume it will remain available in readonly for the foreseeable future? -Did you consider including svn-related meta-data in the converted Git repository? The current Git repository for Papyrus does not seem to include them. On the one hand, it would somewhat clutter the logs. On the other end, it would be helpful for those relying on specific svn revision (especially depending on the answer to the first question). Best regards, -- Alain Le Guennec, R&D Expert Engineer SCADE System Project Manager Esterel Technologies, a wholly-owned subsidiary of ANSYS, Inc. Tel: +33 5 34 60 90 55 --------------------------------------------------------------------------------------------------- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action
in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. On Fri, Jul 12, 2013 at 10:35 AM, LETAVERNIER Camille <Camille.LETAVERNIER@xxxxxx> wrote: Hi, The migration is complete (Based on SVN, revision 11754). The last three commits on SVN (11755 -> 11757) have not been migrated, so you
will need to push them to git again. The repository is: ssh://committer_id@xxxxxxxxxxxxxxx/gitroot/papyrus/org.eclipse.papyrus.git http://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git Note: There are many branches, we still need to cleanup. You may be interested by one
of the following branches: -
master (Kepler/0.10) -
0.8.X-EYY (Indigo/0.8/Topcased branch) The Luna branch doesn’t exist yet. Enjoy
J Camille __________________________ Camille Letavernier +33 (0)1 69 08 00 59 -
camille.letavernier@xxxxxx CEA LIST - Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE) Papyrus :
http://www.eclipse.org/papyrus De :
mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de LETAVERNIER Camille Hi all, We’ve requested a migration from SVN to Git for the Papyrus project: 412746: SVN to Git migration request for Papyrus https://bugs.eclipse.org/bugs/show_bug.cgi?id=412746 The current SVN repository will soon be flagged as Read-only (Most likely early next week). The Git repository will preserve the current structure and history. Regards, __________________________ Camille Letavernier +33 (0)1 69 08 00 59 -
camille.letavernier@xxxxxx CEA LIST - Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE) Papyrus :
http://www.eclipse.org/papyrus
|