3

In our Mercurial repo we added a really big file (and did an hg push), then deleted the big file (and did another push).

Now if someone does an hg clone will they still pull down that big file? I know it won't appear in their working directory as it was deleted, but will the file still be pulled down and stored in Mercurial internal storage?

I'd like to ensure people don't have to pull down the file. I've learned that really big files should be stored outside of Mercurial, so I deleted the file. But I was wondering if people will still be pulling down the big file - in which case I guess I will recreate the repository from scratch.

Brian Tompsett - 汤莱恩
  • 5,753
  • 72
  • 57
  • 129
Marcus Leon
  • 55,199
  • 118
  • 297
  • 429

2 Answers2

6

Of course it will still be in the repository.

You can always update back to older revisions, and if you update back to the revision you got when you committed the file, it'll be there in all its glory.

There are two ways to mitigate this (when you're committing, not now):

  • One of the big-files extensions, these essentially add big files to a secondary repository and link the two, so that if you update to a revision where the file doesn't exist, and you don't already have it, it will not get updated. ie. it's more a "on-demand" style of pulling
  • If the file never changes, keep it available on the network and just create some kind of link to it instead of a full copy

Right now, you got four options:

  • Strip away the changeset that added the file, and all the changesets that came after it. You can do that using the Mercurial Queues extension. Note that you need to do this stripping in all clones. If just one of your users push back the repository that has that file in its history to the central clone, you have the changesets back.
  • Rebuild the repository from scratch manually
  • Using the hg convert command and some filtering, the --filemap option can be used for this
  • Leave it as is. How big is it, will be much of a problem?

Note that rebuilding the repository, either manually or through hg convert will invalidate all clones. Anyone trying to push to your new central clone from an old clone will get a message about unrelated repositories. If any of your users are stupi^H^H^H^H^Hnot smart enough to realize that forcing the push is a bad idea, then you will have problems with this approach.

Lasse V. Karlsen
  • 380,855
  • 102
  • 628
  • 825
4

Yes, the file is still in the history. If you want to delete it completely, you need to use Mercurial Queues — see Editing History on Mercurial wiki.

Just keep in mind this breaks clones as revision IDs change.

Cat Plus Plus
  • 125,936
  • 27
  • 200
  • 224