git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Potapov <dpotapov@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Jakub Narebski <jnareb@gmail.com>,
	Mark A Rada <marada@uwaterloo.ca>,
	git@vger.kernel.org
Subject: Re: Add Gitweb support for LZMA compressed snapshots
Date: Sat, 1 Aug 2009 18:13:04 +0400	[thread overview]
Message-ID: <20090801141304.GB10264@dpotapov.dyndns.org> (raw)
In-Reply-To: <94a0d4530907310845k51dbafbfy8e240467113dfc16@mail.gmail.com>

On Fri, Jul 31, 2009 at 03:45:02PM +0000, Felipe Contreras wrote:
> 
> bzip2 has no advantages whatsoever. AFAIK xz is superior to other
> formats and it would be nice to see git make a technological stance
> encouraging xz.

git is not about encouraging any compression. If you have not noticed,
git-archive produces tar and not tgz (though it would not be difficult
to implement it, because we use zlib anyway). If you like xz and it is
installed on your system, you can always compress tar with it:

git archive HEAD | xz > my-archive.tar.xz

So, I see no reason to have this compression coupled with git.

> 
> > The only reason we have inbuilt gzip and zip support is because the format
> > is so similar to Git's own compression.
> 
> Personally I don't see the point of having zip support.

zip is still a popular format on Windows. If git archive was not able to
produce then creating would require creating tar first, extracting it to
some temporary directory and then creating a zip file. It is not very
efficient process and requires extra efforts, so because we use zlib
compression anyway, it makes perfect sense that we can create zip file
directly.

Dmitry

      parent reply	other threads:[~2009-08-01 14:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30  5:48 Add Gitweb support for LZMA compressed snapshots Mark A Rada
2009-07-30  7:44 ` J.H.
2009-08-01  7:43   ` Alex Riesen
2009-08-01 14:34     ` Dmitry Potapov
2009-08-01 14:38     ` André Goddard Rosa
2009-08-01 14:58     ` Jim Meyering
2009-08-01 18:51       ` Alex Riesen
2009-07-30  7:52 ` Johannes Schindelin
2009-07-30  8:31 ` Jakub Narebski
2009-07-30  8:43   ` Johannes Schindelin
2009-07-31 15:45     ` Felipe Contreras
2009-08-01 12:34       ` Johannes Schindelin
2009-08-01 13:10         ` Felipe Contreras
2009-08-01 14:04           ` Erik Faye-Lund
2009-08-01 16:07             ` Mark A Rada
2009-08-01 21:39               ` Erik Faye-Lund
2009-08-01 14:13       ` Dmitry Potapov [this message]

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=20090801141304.GB10264@dpotapov.dyndns.org \
    --to=dpotapov@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=marada@uwaterloo.ca \
    /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).