olemis at gmail
Jul 6, 2009, 1:41 PM
Post #2 of 2
(262 views)
Permalink
|
|
Re: A few doubts about Trac Version Control API
[In reply to]
|
|
On Mon, Jul 6, 2009 at 9:00 AM, Olemis Lang<olemis [at] gmail> wrote:
> Hello everybody !
>
> I was implementing TracGViz version 1.3.3 (which is almost ready ;)
> and the side-effect is that I have a few doubts. I'd appreciate if
> someone either replies with the answer or with a link to the page(s)
> where I could find further info about the subjects involved ;)
>
> Here are some of them :
>
> About Trac Version Control API :
>
> - The question is related to history methods (e.g. Repository.get_path_history,
> and Node.get_history) in VCS API. They generate data related to different
> changesets or revisions. My Q is the following : Do this methods return
> younger revs first (i.e. if `repos.rev_older_than(rev1, rev2)` then
> all data about `rev2` is returned before data about `rev1`) ?
> I mean is it a postcondition of these methods, or is it possible that values
> be generated at random or following a different order ? All this is
> considering the different connectors available these days and maybe others ;)
>
BTW I also need this in order to impl VersionControlRPC.
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
|
