From: "J.C. Pizarro" <jcpiza@gmail.com>
To: git@vger.kernel.org
Subject: Re: How small is git-packed mailing list vs zipped mailing list?
Date: Sat, 23 Feb 2008 06:34:54 +0100 [thread overview]
Message-ID: <998d0e4a0802222134r1c96b39bt2d34f3fb2289c67f@mail.gmail.com> (raw)
In-Reply-To: <998d0e4a0802222103x7b42b849q950a2a3c9b0d3550@mail.gmail.com>
On 2008/2/23, J.C. Pizarro <jcpiza@gmail.com>, i wrote:
> Not all inside of git repository data is source code used for
> versioning control, but the mailing lists are pushed too into git repo!
>
> Is there any idea of
>
> How small is a git packed mailing list vs zipped mailing list?
>
> ;)
>
It thanks to the delta scheme, minimum spanning tree and zlib of the git packer.
1. For git, it's better to commit splitted monthly-files
(the atomic messages have some redundancy in the replies and forwards).
2. For zip, it's better to zip non-splitted monthly-files.
next prev parent reply other threads:[~2008-02-23 5:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 5:03 How small is git-packed mailing list vs zipped mailing list? J.C. Pizarro
2008-02-23 5:34 ` J.C. Pizarro [this message]
[not found] ` <2050562.kVPcb3l6ef@mid.thomas-huehn.de>
2008-02-23 9:26 ` J.C. Pizarro
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=998d0e4a0802222134r1c96b39bt2d34f3fb2289c67f@mail.gmail.com \
--to=jcpiza@gmail.com \
--cc=git@vger.kernel.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).