git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Add Gitweb support for LZMA compressed snapshots

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Aug 1, 2009, 13:10 UTC
Message-ID
<94a0d4530908010610n31261414yc08060f3de9c115f@mail.gmail.com>
In-Reply-To
<alpine.DEB.1.00.0908011431060.8306@pacific.mpi-cbg.de>

On Sat, Aug 1, 2009 at 12:34 PM, Johannes Schindelin<Johannes.Schindelin@gmx.de> wrote:

Show 20 quoted lines
> Hi,
>
> On Fri, 31 Jul 2009, Felipe Contreras wrote:
>
>> On Thu, Jul 30, 2009 at 8:43 AM, Johannes
>> Schindelin<Johannes.Schindelin@gmx.de> wrote:
>> > Hi,
>> >
>> > On Thu, 30 Jul 2009, Jakub Narebski wrote:
>> >
>> >> BTW. I wonder if it would be good idea to add support for this format
>> >> directly to git-archive...  OTOH it would mean additional dependency.
>> >
>> > I don't think it would be a good idea; we do not have bzip2 support
>> > either.
>>
>> bzip2 has no advantages whatsoever.
>
> Bzzzzt.  Wrong.  Just because you cannot see them does not mean it has no
> advantages.

All right, most the time you compress once, and multiple people uncompress multiple times. Therefore the path that should be optimized is the decompression, that leaves bzip2 out of the picture.

You can think of advantages of bzip2 in more esoteric cases where the compression time is also important. I don't think that's the case here. Actually it might be if gitweb is not caching the tarballs, but if that's the case I wouldn't say it's an advantage of bzip2.

Show 5 quoted lines
>> AFAIK xz is superior to other formats and it would be nice to see git
>> make a technological stance encouraging xz.
>
> Bzzzt. Wrong again.  Git's mission in life is not to encourage one
> compression over another.

Git's mission in life is not promoting asciidot either, but it's doing that unintentionally by merely using it.

Show 11 quoted lines
> If at all, the only compression Git actually does promote in a sense is
> zlib compression.
>
>> > 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.
>
> Personally, I see the point of having zip support.  It makes things easy
> for Windows users.  And it's an established format, much more so than
> tar.gz.
Windows can't extract .tar.gz?
-- 
Felipe Contreras
Previous: Johannes SchindelinNext: Erik Faye-Lund
Message 13 of 17 in “Add Gitweb support for LZMA compressed snapshots”
  1. Mark A RadaJul 30, 2009
  2. J.H.Jul 30, 2009
  3. Alex RiesenAug 1, 2009
  4. Dmitry PotapovAug 1, 2009
  5. André Goddard RosaAug 1, 2009
  6. Jim MeyeringAug 1, 2009
  7. Alex RiesenAug 1, 2009
  8. Johannes SchindelinJul 30, 2009
  9. Jakub NarebskiJul 30, 2009
  10. Johannes SchindelinJul 30, 2009
  11. Felipe ContrerasJul 31, 2009
  12. Johannes SchindelinAug 1, 2009
  13. Felipe ContrerasAug 1, 2009
  14. Erik Faye-LundAug 1, 2009
  15. Mark A RadaAug 1, 2009
  16. Erik Faye-LundAug 1, 2009
  17. Dmitry PotapovAug 1, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.