[Pharo-project] About this MC extensions
Name: Monticello-jf.321 Author: jf Time: 23 October 2008, 8:14:55 pm UUID: 94116b6e-f3dc-da49-b5ed-d90ba5b4c9f3 Ancestors: Monticello-AlexandreBergel.320 The Monticello UI used to support "branches" by allowing multiple version segments separated by periods. So, for example, if you had a version called: my-package-jf.testbranch.4 the next suggested version name would be: my-package-jf.testbranch.5 You could also have my-package-jf.testbranch.subbranch.4. The version of MC in Pharao no longer allows this and suggests my-package-jf.5 instead. This version fixes the behaviour to keep everything up to the author initials and everything between the initials and the last period. New initials and new last number are provided. ======================== Hi since we do not really understand the implications of that changes when the authors have a . in their name we move it to the treated inbox and invite jf to discuss it in the list and resubmit a fix. Stef and Marcus
since we do not really understand the implications of that changes when the authors have a . in their name we move it to the treated inbox and invite jf to discuss it in the list and resubmit a fix.
That's a problem indeed. Seaside and many other (mostly commercial) projects use named branches excessively. The $. is used to separate the branch from the author initials. Unfortunately this support is broken in Pharo and the fix solves the issue we have with the Pharo Monticello. I think it is crucial to any version control system to properly support named branching. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch
So lukas should we merged the changes proposed by jf (which should sign the agreement). Can you check with the latest updates>? Stef On Oct 25, 2008, at 6:56 PM, Lukas Renggli wrote:
since we do not really understand the implications of that changes when the authors have a . in their name we move it to the treated inbox and invite jf to discuss it in the list and resubmit a fix.
That's a problem indeed.
Seaside and many other (mostly commercial) projects use named branches excessively. The $. is used to separate the branch from the author initials. Unfortunately this support is broken in Pharo and the fix solves the issue we have with the Pharo Monticello. I think it is crucial to any version control system to properly support named branching.
Cheers, Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (2)
-
Lukas Renggli -
Stéphane Ducasse