[MERGE] add stop_rule to Branch.iter_merge_sorted_revisions()
Ian Clatworthy
ian.clatworthy at internode.on.net
Tue Jan 27 00:18:51 GMT 2009
I wrote on 25/01/2009:
> It looks like 'inclusive' isn't flexible enough. I'm going to add a
> parameter called (something like) stop_rule with values of:
>
> * "exclude" - leave the stop revision out of the result
> * "include" - put the stop revision in the result
> * "with-merges" - put the stop revision and nested merges in the result.
Attached.
> Any thoughts on the best default? It's currently "include" but
> the API has only existed for 24 hours so I'll change it to
> "exclude" (say) if we think that's the most common case.
I've made exclude the default. I don't think it matters much and
I'm happy to choose a different one if anyone feels strongly.
Ian C.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: stop-rule-ismr.patch
Type: text/x-diff
Size: 11665 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090127/5ed7d88a/attachment.bin
More information about the bazaar
mailing list