Re: BK, deltas, snapshots and fate of -pre...

[Jeff Garzik <garzik@havoc.gtf.org>]

On Sun, Apr 21, 2002 at 10:57:06AM -0700, Larry McVoy wrote:
> On Sun, Apr 21, 2002 at 01:49:55PM -0400, Jeff Garzik wrote:
> > I know, but graphical is useless to me...
> > Give me text/plain GNU-style patches, that I can spit out without
> > requiring X. :)
> 
> I did.  Install those triggers and you've got it.  Sorry to sound
> uncooperative but the trigger mechanism is there to handle this, and
> email notification, and automatic mirroring, and ...

(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