(did you miss that we're off on a tangent? :))
If we are talking about 'bk diffs -C' for Linus, agreed.
But you started talking about the nifty feature of seeing what you
downloaded in the last 'bk pull'.
Triggers are completely useless for "show me what the next-to-last
'bk pull' downloaded, in GNU patch style." It's unrealistic to assume
that everybody is gonna set up triggers and their own cset GNU patch
archive, just to provide themselves with this capability. Especally
when (IMO) bk can generate that stuff on the fly.
If BK knows a single basic unit of information -- the list of csets
downloaded in each 'bk pull' -- then it should be able to generate
patches for those csets. Or at the very least, have a bk command
that spits out that list of csets, and user-written scripts take it
from there.
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/