On Wed, Jan 30, 2002 at 11:58:11PM -0500, Alexander Viro wrote:
> Suppose I have 5 deltas - A, B, C, D, E. I want to kill A.
If you just want to make A's changes go away, that's trivial:
bk get -e -xA foo.c
bk delta -y"kill A's changes"
all done.
If you want to make A go away out of the graph, that's only possible if
you have the only copy of the graph containing A. Since BK replicates
the history, you only get to do what you want before you push your changes
to someone else. No surgery after you let the cat out of the bag.
You have a repository and you haven't propogated all this stuff to
someplace else, then this is easy, we'll just rebuild the history minus A.
You or I could write a shell script using BK commands to do it in about
10 minutes.
It's a distributed, replicated file system which uses the revision history
to propogate changes. If you don't care about talking to anyone else,
you can do whatever you want. If you want to give someone your history
and then change it, no way. That's rewriting what happened.
Now does it make more sense?
-- --- 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/
This archive was generated by hypermail 2b29 : Thu Jan 31 2002 - 21:01:31 EST