hi I'm currently looking at mercurial for some maven managed projects. It looks like named branches would be the way to go there (more on it at the end of this mail for those interested), but I read on the mercurial wiki that named branches are to be avoided, but without providing much details. Up to now, the only drawback spotted is having many old branches in the branches view, when switching, but it doesn't look intriguing...
So, in the end, is there any "strong" reason to avoid named branches ? Would 1000 of them kill performance or something similar ? Thanks in advance zedros PS : why named branches look like the way to go ? The maven projects used rely heavily on workspace resolution, available through the m2eclipse plugin. As such, having different projects open from the same pom would be quite an issue. Whereas using named branches and switching between them look like perfectly solving this issue... -- You received this message because you are subscribed to the Google Groups "MercurialEclipse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mercurialeclipse?hl=.
