From: Sverre Rabbelier <srabbelier@gmail.com>
To: Tim Blechmann <tim@klingt.org>, Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: git svn unhandled.log compression
Date: Thu, 19 Mar 2009 12:06:01 +0100 [thread overview]
Message-ID: <fabb9a1e0903190406r31396bbao2717f94d7269b50a@mail.gmail.com> (raw)
In-Reply-To: <gps05u$905$1@ger.gmane.org>
Heya
[full message quoted as now ccing Eric]
On Thu, Mar 19, 2009 at 00:30, Tim Blechmann <tim@klingt.org> 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
next prev parent reply other threads:[~2009-03-19 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 23:30 git svn unhandled.log compression Tim Blechmann
2009-03-19 11:06 ` Sverre Rabbelier [this message]
2009-03-19 12:18 ` Tim Blechmann
2009-03-19 17:55 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fabb9a1e0903190406r31396bbao2717f94d7269b50a@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=tim@klingt.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).