Remove, and leave nothing behind.

[Talden]

On Thu, Mar 5, 2009 at 8:56 AM, Jari Pennanen <ciantic at mbnet.fi> wrote:
> Hi!
>
> I managed to commit (several revisions ago) client information to one
> of my branch and now I'd like to remove those files persistently, so
> that if I publish the branch it won't get leaked.
>
> Is there a way to remove, and make sure nothing is left behind? Remove
> so that no revert or history could ever recover those files.

If you haven't published yet then you could go back to before the
point you added then information and then replay the safe commits
omitting the one containing unsafe content.  I haven't looked at how
you would achieve this but I expect the rebase plugin is useful here.

If you've already published then others already have this information
and removing it merely breaks the ancestry of derived branches but
doesn't remove anything from those derived branches.

--
Talden