Hi,
Thanks for your recommendations. I'll try the unrecord method
suggested by Zooko first since it seems to be the safest route. If
that fails, then I'll do the manual thing. No problem with repo
backups. I have several complete tarballs of the repo because I have a
cronjob that automatically
Hello,
I managed to remove the file completely from the repo by using both
unrecord and manual repo editing.
Here are some notes regarding this:
o The patch that originally added the secret file also added other
files that were subsequently modified by other patches.
o I had the presence of
Hello everyone,
I just realized that I recorded a patch that included a file that
contained sensitive (config file containing database passwords, secret
hashes, etc.) information. I know I should have taken the time to
include it in prefs/boring, but I didn't. Unrecording this patch will
also
You're going to have to unrecord the patch that added the file.
Why do other patches depend upon it? Possible because they depend upon other
stuff in the initial patch (rather than that they depend on the secret file!).
Try something like this:
darcs get origrepo expurgatedversion
cd
On Wed, Jun 08, 2005 at 05:05:07PM +, Nimrod A. Abing wrote:
I would
like to completely remove this file, including any history in the
repository that will allow it to be pulled again. Is there a way to do
this?
I think the
On Wed, Jun 08, 2005 at 09:09:31PM +0200, Tommy Pettersson wrote:
It is probably bad and unsafe in many ways to alter a repo
by hand. Make sure the new repo works and keep the old repo
as a backup.
It's generally a bad idea to edit patches by hand--mostly because most
people wouldn't know if
