From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org, bitkeeper-announce@bitmover.com
Subject: Re: BKWeb Feature request [Was: BK license change]
Date: Sat, 24 Aug 2002 08:11:41 -0700 [thread overview]
Message-ID: <20020824081141.D17092@work.bitmover.com> (raw)
In-Reply-To: <20020824171245.C1889@mars.ravnborg.org>; from sam@ravnborg.org on Sat, Aug 24, 2002 at 05:12:45PM +0200
> Is it possible somehow to sort the cset(s) according to the time they were
> applied to the local tree, and not when they were originally committed?
If this is a correct statement of what you want, we're building it:
Instead of seeing events in time order of creation, you want to
see the events in order of arrival in a particular repository.
I agree that the current view is useless when what you want to know is
when did this change finally make it into the tree?
We're working on a "stack" of incoming events. BK/Web will use this to
give you the display you want and bk undo will be able to use this to
roll your repository backwards by "popping" the stack. You could do
while true
do bk undo -sf
done
and when it gets done, you'll have no repository, it will have popped it
away. bk unpull will just be come a special case of popping the stack.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
prev parent reply other threads:[~2002-08-24 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-24 0:39 RFC: BK license change Larry McVoy
2002-08-24 1:26 ` [Bitkeeper-announce] " david parsons
2002-08-24 15:12 ` BKWeb Feature request [Was: BK license change] Sam Ravnborg
2002-08-24 15:11 ` Larry McVoy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020824081141.D17092@work.bitmover.com \
--to=lm@bitmover.com \
--cc=bitkeeper-announce@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox