Re: reverting a file in a repository
"Benjamin A. Collins" <[email protected]>
| Newsgroups | gmane.comp.version-control.bitkeeper.user |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Sep 06, 2004 at 07:40:06PM -0700, Larry McVoy wrote:
> 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.
<snip>
Larry, thanks for the tip. As it turns out, another member of my team
had done a 'bk rm' on the file in question which created obvious
difficulties. What I ended up doing was cloning the master repository
right up to the point where the original mistake was made, and then
used stripdel to back out the one mistake. Then I used treediff to
get the changes that I had excluded and brought the fixed repository
up to date using 'bk import'.
Thanks again.
bc
--
-------------------------------------------------
| Benjamin A. Collins <[email protected]> |
| http://people.cs.tamu.edu/bcollins/ |
-------------------------------------------------
_______________________________________________
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.