# git svn unhandled.log compression 4 messages from 2009-03-18 to 2009-03-19. Participants: Tim Blechmann, Sverre Rabbelier, Eric Wong. Thread: https://gitlist.dev/t/18390 ## Tim Blechmann, 2009-03-18 23:30 Subject: git svn unhandled.log compression Message-ID: URL: https://gitlist.dev/e/gps05u%24905%241%40ger.gmane.org ``` hi all, is there a way to compress the unhandled.log files, generated by git svn? tracking several projects with git svn, the unhandled.log files are larger, than the actual data ... e.g. the mirror of the svn repository of the boost library gives me: 135M .git/objects 283M .git/svn the unhandled.log files can be compressed at pretty high rates, these are the differently compressed files from the trunk of boost svn: 9.0M unhandled.log 584K unhandled.log.gz 396K unhandled.log.bz2 344K unhandled.log.lzma i am not familiar with the git svn codebase, so i am not sure, whether it is feasible to implement a compression of the unhandled.log files, but it would definitely save me quite a lot of hd space ... thnx, tim -- tim@klingt.org http://tim.klingt.org The most wonderful opportunity which life offers is to be human. Henry Miller ``` ## Sverre Rabbelier, 2009-03-19 11:06 Subject: Re: git svn unhandled.log compression Message-ID: URL: https://gitlist.dev/e/fabb9a1e0903190406r31396bbao2717f94d7269b50a%40mail.gmail.com In-Reply-To: ``` Heya [full message quoted as now ccing Eric] On Thu, Mar 19, 2009 at 00:30, Tim Blechmann wrote: > is there a way to compress the unhandled.log files, generated by git svn? > tracking several projects with git svn, the unhandled.log files are > larger, than the actual data ... > > e.g. the mirror of the svn repository of the boost library gives me: > 135M    .git/objects > 283M    .git/svn > > the unhandled.log files can be compressed at pretty high rates, these > are the differently compressed files from the trunk of boost svn: > 9.0M    unhandled.log > 584K    unhandled.log.gz > 396K    unhandled.log.bz2 > 344K    unhandled.log.lzma > > i am not familiar with the git svn codebase, so i am not sure, whether > it is feasible to implement a compression of the unhandled.log files, > but it would definitely save me quite a lot of hd space ... On that note, Eric, what does the unhandled.log file do in the first place? It's name would suggest it lists all revisions that aren't handled yet, but the contents of the file seem to only grow over time, what gives? -- Cheers, Sverre Rabbelier ``` ## Tim Blechmann, 2009-03-19 12:18 Subject: Re: git svn unhandled.log compression Message-ID: <49C23815.5010204@klingt.org> URL: https://gitlist.dev/e/49C23815.5010204%40klingt.org In-Reply-To: ``` >> i am not familiar with the git svn codebase, so i am not sure, whether >> it is feasible to implement a compression of the unhandled.log files, >> but it would definitely save me quite a lot of hd space ... > > On that note, Eric, what does the unhandled.log file do in the first > place? It's name would suggest it lists all revisions that aren't > handled yet, but the contents of the file seem to only grow over time, > what gives? according to the man page, it logs unhandled svn properties tim -- tim@klingt.org http://tim.klingt.org art is short - life is long Jack Kerouac ``` ## Eric Wong, 2009-03-19 17:55 Subject: Re: git svn unhandled.log compression Message-ID: <20090319175514.GC23127@dcvr.yhbt.net> URL: https://gitlist.dev/e/20090319175514.GC23127%40dcvr.yhbt.net In-Reply-To: <49C23815.5010204@klingt.org> ``` Tim Blechmann wrote: > >> i am not familiar with the git svn codebase, so i am not sure, whether > >> it is feasible to implement a compression of the unhandled.log files, > >> but it would definitely save me quite a lot of hd space ... > > > > On that note, Eric, what does the unhandled.log file do in the first > > place? It's name would suggest it lists all revisions that aren't > > handled yet, but the contents of the file seem to only grow over time, > > what gives? > > according to the man page, it logs unhandled svn properties Yup, it logs things that git-svn currently cannot handle. It's meant to be machine parseable so other tools[1] can process them after-the-fact. I would accept a patch for a command like "git svn gc" to deal with compressing them. [1] - as far as I know there are none -- Eric Wong ```