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

Re: gitweb feature request: tarball for each commit

From
A Large Angry SCM <gitzilla@gmail.com>
Date
Sep 8, 2005, 14:03 UTC
Message-ID
<4320449D.2070306@gmail.com>
In-Reply-To
<20050908113207.GA30178@vrfy.org>
Kay Sievers wrote:
Show 12 quoted lines
> On Thu, Sep 08, 2005 at 10:45:45AM +0200, Sven Verdoolaege wrote:
>>On Thu, Sep 08, 2005 at 04:30:22PM +1200, Martin Langhoff wrote:
>>>Actually... should get it done. I'll see if I can sneak it in sometime soon... 
>>This has been done at least twice already.
>>See e.g., http://www.liacs.nl/~sverdool/gitweb.cgi?p=gitweb.git;a=summary
>>Check the archives for the other implementation.
> 
> Yes, this is nice for smaller projects. But I don't think, that we want
> to do such a thing on the kernel.org servers. We already have the daily
> snapshots and individual patches can be downloaded from gitweb. Anybody
> else should use git/cogito instead of letting the server packaging a huge
> tree for every requested revison, I think.

I think this is a very useful feature for for some, but not all, repositories. Default it to off and have a magic file (like git-daemon), or a config variable turn it on.

Previous: Kay SieversNext: Martin Langhoff
Message 4 of 5 in “gitweb feature request: tarball for each commit”
  1. Martin LanghoffSep 8, 2005
  2. Sven VerdoolaegeSep 8, 2005
  3. Kay SieversSep 8, 2005
  4. A Large Angry SCMSep 8, 2005
  5. Martin LanghoffSep 8, 2005

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.