ref service: ListBranchNamesContainingCommits
At this point, the ordering of results is arbitrary. We don't expect that to be a problem until after the first end-to-end experiments. Implicitely expected ordering is specified in comment. Implementation is probably somewhat inefficient. It's a bit frustrating that in Mercurial we know right away to which branch a commit relates (contrary to Git) but still have to do all these ancestry computations. But it would be easy to be wrong if trying to be smarter.
Please register or sign in to comment