Re: reverting a file in a repository

On Mon, Sep 06, 2004 at 10:21:59AM -0500, Benjamin A. Collins wrote:
> I hade a mistake in my repository by checking in a file that had
> sensitive information in it.  I didn't realize it at the time and it
> has been committed and pushed.  Simply patching out the changes and
> re-committing the file isn't a good solution for me because the
> sensitive info is still stored in the repository and viewable.  Is
> there a way to completely rip a cset (or a partial cset for a
> particular file) out of the repository?

There are a couple of ways.  The main thing you have to worry about is 
hunting down the other repos to which it has pushed and fix them as well.
If you have a master repo and you have access to that then do it there 
and have people reclone.

The easiest way is to go find the file that has the delta in and run

	bk stripdel -C -r$REV $FILE

That will remove all traces of that delta (note: $REV must be "+", you can't
strip deltas in the middle of the history).

You aren't done because the next time you run check it will complain, as it
should, that that delta is missing.  If you run

	bk -r check -agg > LIST
	cat LIST	# make sure it has one delta in it from that file
	bk -R gone - < LIST
	bk commit

then you'll be all set.  Run a bk -r check -acv just to be sure.
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com
_______________________________________________
Bitkeeper-users mailing list
[email protected]
http://bitmover.com/mailman/listinfo/bitkeeper-users
To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.