Dave's recent changes replace the implementation of Repo.revision_history() with a simple call to Walker.
Since this is the only graph-related function in Repo at the moment, I wonder if it would make sense to deprecate it. In all but the simplest case it's probably a better idea to use Walker. Repo also already has enough methods as-is. Alternatively, perhaps we can just provide a .get_walker() method toreplace .revision_history() which is more discoverable ? Thoughts? Cheers, Jelmer
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mailing list: https://launchpad.net/~dulwich-users Post to : [email protected] Unsubscribe : https://launchpad.net/~dulwich-users More help : https://help.launchpad.net/ListHelp
