> All you need to do is save the starting and ending cset revs as keys,
> and then send those into bk export -tpatch. So a trigger which saved
> top of trunk on a stack is all you need, the rest is a tiny amount of
> perl/shell. Write it, send it to me, if people like it, we'll roll it
> into the mainline release.
In order to implement multiple 'bk undo' stack as you described, you
need to store or deduce that info anyway. If I wrote it, wouldn't I be
duplicating work (or doing work for you)?
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/