Am Freitag, 18. November 2005 23:37 schrieb Lele Gaifax:
> >>>>> "Wolfgang" == Wolfgang Jeltsch <[EMAIL PROTECTED]> writes:
>
>     Wolfgang> What about brances which are represented by multiple
>     Wolfgang> repositories?  Do I have to create a separate Trac
>     Wolfgang> project for every branch?
>
> Yes, unfortunately. It's my top desire to have resources to implement
> the multi repo feature. Search in the Trac wiki, you'll find some
> references.

Hello again,

from http://projects.edgewall.com/trac/ticket/2086:

        as an extension to the above scheme, link to changesets could be written
        [repos1/<the_changeset>], in case there could be an ambiguity in the
        changeset identifiers. But generally, the better SCMs would provide 
some kind
        of changeset identifier that is repository independent, right? (at least
        Mercurial does it that way) 
        In this situation, there wouldn't even be a need to disambiguate the
        changeset.

As far as I know, darcs has repository-independent identifiers for patches, so 
it would be better to use these in links to changesets.  Is there any effort 
in changing Trac on darcs to use darcs' patch identifiers instead of the 
Subversion-inspired numeric identifiers which are repository-dependant?

> [...]

> ciao, lele.

Best wishes,
Wolfgang

_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users

Reply via email to