Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Collaborative Work with File approach

Hi,

 

We have two different naming schemes:

 

-          bugs/123456

-          committers/committerid/QuickDescription

 

So, this naming is correct.

 

(BTW, I find the first option complicated, because it is not obvious to find the purpose of a branch from just a bug ID. Something like bugs/123456-QuickDescription might be better)

 

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 Cedric Dumoulin
Envoyé : lundi 4 novembre 2013 15:50
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Collaborative Work with File approach

 


 Hi,

DAUSSY Arthur a écrit :

A new branch adaussy/FileCollaborativeWork-420977 will be created to support this effort.

See bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=420977.

If you have any information on APIS for this king of operation please tell me.

  Don't we have a standardized naming scheme for branches like this ?
 
  Cedric


Back to the top