Georg wrote: > Sorry to be insisting, but I need some more information.
No problem, and it's a nice timing, as I'm just working on the Trac revision log. > > It appeared to me the history log is provided in > MercurialNode.get_history. There are two cases here, one for > directories (including the whole tree) and one for files: So 3 cases. In the first (no path specified), we just go linearly down all the changesets. The order is the sequential order of the changesets. The second is for the directories, where we use walkchangerevs. The last was supposed to be an optimization, as the whole history of a file is contained in its revlog. But the disadvantage of that is that we would have to reimplement the follow_first logic and also the follow copy, which is probably already there in walkchangerevs. So yes, it would be interesting to simplify this and have everything use walkchangerevs, with the follow_first logic. -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
