Tree._iter_changes(specific_files=[]) behaviour.

[Wouter van Heyst]

On Sat, Jul 14, 2007 at 10:56:13AM -0400, Aaron Bentley wrote:
> Wouter van Heyst wrote:
> > set of interesting_ids, but now it is left to tree._iter_changes. When
> > you pass specific_files=[] to tree._iterchanges it iterates over all the
> > changes between the two trees.
> > 
> > I think my question is, what do we want _iter_changes(specific_files=[])
> > to do? Klaus ran into similar questions for tree.{revert,add,commit},
> > they're not consistent in handling files=[].
> 
> I think the empty list should cause no files to be selected, and None
> should cause all files to be selected.

That's the api I'd prefer. How do we get there?

Wouter van Heyst