The pickle jar is 600kb bzip2-compressed (hence probably un-diffable by
git). So every change to it inflates our repo size by about 1%. IMHO we
should either untar/decompress it to track its content, or turn it into a
downloadable tarball. Suggestions? Volunteers?
This comes up in http://trac.s
On Wed, Feb 09, 2011 at 04:51:14AM -0800, Anne Schilling wrote:
> For #8911 the new pickle jar was just attached. So I added this file
> to #10632. Probably you can do the same for #7922 (but then the tickets
> might not commute if both change the pickles).
Yeah, that pickle jar procedure is not p
Hi there,
it seems my Singular update patches produce pickle jar failures. I am not
aware of any documentation guiding me how to debug this. I guess I could just
dive in (and learn the hard way) but wonder if anybody can share a few tips?
Cheers,
Martin
--
name: Martin Albrecht
_pgp: http://
