On Fri, Oct 17, 2014 at 10:16 AM, Tony Papadimitriou <to...@acm.org> wrote:
> Not being sure I understood your approach completely, and without > knowing fossil’s internals, but knowing that it uses SQL for a lot of its > work, I think that mostly the related SQL would have to change. > > I believe a simple loop approach would just print FINFO for each file > separately before processing the next one, right? > That's what i was thinking. > But that would be out of historic order. > The idea is to get the history of all matched files in the correct order, > so if files A and B change, you want a display like this: > Okay, that's getting a bit over my head ;). i will take a look after work, but make no promises. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
