Recent developer mistakes have involved accidentally committing quite large JAR files to repository history when they should have been taken from external binaries. Even if corrected in sources, the changesets continue to consume a lot of space in history that cannot be undone.
We should have a Mercurial hook preventing anyone from pushing any changeset containing a new or modified ZIP file. (Even if you need to store e.g. sample projects for tests, it is best to keep them unpackaged in the repo since that will compress much better and it is easier to follow modifications.)
Based on code in the file http://hg.netbeans.org/nb-hooks/file/3101141d5868/forbid_external.py , I would say that all file with extension zip, jar, gz, bz2, gem and dll are forbidden to commit.
Could you please tell me what miss in the mentioned hook?
(In reply to comment #1)
> Based on code in the file
> http://hg.netbeans.org/nb-hooks/file/3101141d5868/forbid_external.py , I would
> say that all file with extension zip, jar, gz, bz2, gem and dll are forbidden
> to commit.
Only in external/ or release/ dirs. The problem is ZIPs being committed from other places.