Jeff Hamilton wrote:
support for Mercurial/etc go next. Plus we should try to get feedback
from the folks who worked on Darcs/BazaarNG/Perforce support.
Jason Parks and I have been working on the p4trac plugin with 0.10. One
major thing that would make the Perforce plugin more useful is to have the
concept of both file revisions and repository revisions (Perforce calls
these change numbers). I hacked the trac core back in December to allow
this and things like the changset viewer worked much better,
We could add a Node.filerev method, which would be by default
the same as Node.rev. The Revision log could show the filerev in
the Rev. column and the repository revision in the Chgset colum.
But that might be a problem for the Rev column for directories,
if there's no filerev info for them
but there was
still a lot of ambiguiity in the system between change numbers and file
revisions.
Please mention where it would help to use filerevs instead of changeset
numbers.
Perforce makes it especially hard since directories aren't
actually objects like they are in Subversion, so you don't have revision
numbers for changes to directories, you only have change numbers for
changes contained in that directory, and optionally it's sub directories.
I think it's helpful that way: you have an overview of the last activity
that occurred in that folder. Of course, that's something that can be
costly if the backend doesn't support that directly, but hopefully
I'll find a generic way to get that information from the db cache.
-- Christian
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
