Tim Pillinger

> Conflict resolution looks good Thank you @hjoliver

> Something's gone wrong git-wise Rebased ... poorly 

> ``` > [scheduling] > initial cycle point = 2012 > [[dependencies]] > graph = foo > [[[T00]]] > graph = bar > [runtime] > [[foo,bar]] > ``` > >...

> I think this will do Don't get me wrong, it's wierd and complex now. I'm not thrilled. I also cannot justify spending too much time on code which I...

> > [wxtim](https://github.com/wxtim) requested a review from [MetRonnie](https://github.com/MetRonnie) > > @wxtim, you have an outstanding review comment. I think that I was waiting for Ronnie and you finish the discussion....

@MetRonnie - I've used your words. Please merge at your leisure.

I thought we'd documented this somewhere, but presumable skip mode will need the ability to set which (if any) optional outputs are satisfied by the skipped task? (And I feel...

> If you mark a task to be skipped, but it has an xtrigger prerequisite, will it still need to wait fit the xtrigger to be successful before it runs?...

> I can just see an edge case where one xtrigger is used for two tasks, and only one is skipped. I think that the skipping of the xtrigger will...

The Python 7 and 8 Docstrings contain the following info: ``` For backward compatibility, if number of arguments is less than or equal to 2, the command assumes the classic...