Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 21 Apr 2002 14:27:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 21 Apr 2002 14:26:22 -0400 Received: from bitmover.com ([192.132.92.2]:48539 "EHLO bitmover.com") by vger.kernel.org with ESMTP id ; Sun, 21 Apr 2002 14:26:08 -0400 Date: Sun, 21 Apr 2002 11:26:06 -0700 From: Larry McVoy To: Jeff Garzik Cc: Alexander Viro , Linus Torvalds , Ian Molton , linux-kernel@vger.kernel.org, Wayne Scott Subject: Re: BK, deltas, snapshots and fate of -pre... Message-ID: <20020421112606.T10525@work.bitmover.com> Mail-Followup-To: Larry McVoy , Jeff Garzik , Alexander Viro , Linus Torvalds , Ian Molton , linux-kernel@vger.kernel.org, Wayne Scott In-Reply-To: <20020421102339.E10525@work.bitmover.com> <20020421133225.F4479@havoc.gtf.org> <20020421103923.I10525@work.bitmover.com> <20020421134500.A7828@havoc.gtf.org> <20020421104725.K10525@work.bitmover.com> <20020421134955.C7828@havoc.gtf.org> <20020421105706.M10525@work.bitmover.com> <20020421140753.C8142@havoc.gtf.org> <20020421111450.P10525@work.bitmover.com> <20020421142447.G8142@havoc.gtf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Apr 21, 2002 at 02:24:47PM -0400, Jeff Garzik wrote: > On Sun, Apr 21, 2002 at 11:14:50AM -0700, Larry McVoy wrote: > > On Sun, Apr 21, 2002 at 02:07:53PM -0400, Jeff Garzik wrote: > > > Triggers are completely useless for "show me what the next-to-last > > > 'bk pull' downloaded, in GNU patch style." > > > 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)? Perhaps. You'd also be getting your needs met on your schedule, not mine. -- --- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm - 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/