Re: gitweb: View graphes & get tar

From: Andreas Ericsson <ae@op5.se>
Date: Feb 9, 2006, 12:11 UTC
Message-ID: <43EB3158.8070003@op5.se>
In-Reply-To: <4fb292fa0602090312k1607e42fu88e03b788d339390@mail.gmail.com>

Bertrand Jacquin wrote:

Show 34 quoted lines

> On 2/9/06, Alan Chandler <alan@chandlerfamily.org.uk> wrote:
> 
>>On Wednesday 08 February 2006 23:34, Bertrand Jacquin wrote:
>>
>>
>>I have it set up so that when I push a tag into my public git repositories,
>>that a post-update hook creates a tarball of the site and puts it into the
>>download directory.
>>
>>The hook is of the following form
>>
>>#!/bin/sh
>>#
>># This script is used to create a tarball of the project and place it into the
>>"files"
>># directory of the web site whenever a release is tagged in the repository
>>#
>>PROJECT=akcmoney
>># this should look at each positional parameter
>>for ref ; do
>>#if its a tag then create a tarball
>>        if [ "${ref:0:10}" == "refs/tags/" ] ; then
>>                git-tar-tree ${ref:10} $PROJECT | gzip -9
>>
>>>/var/www/chandlerfamily/files/$PROJECT/$PROJECT-${ref:10}.tar.gz
>>
>>        fi
>>done
> 
> 
> That's ok, but with that I couldn't get a tar for _not_ the current
> tree. If i want to get a tar tree for 2 months old in not master
> branch, I can't with that. The idea here is the create the tar on the
> fly, on the user demand.

This should be really trivial to implement, although I seriously doubt its usefulness, not to mention that for large projects it would be painfully slow. The only valid reason someone has to get a tar-ball of a random development point is to debug it, and for that they should check out the whole repo anyways, which will enable them to use the excellent bisect tool.

> And also, I use http push so hooks can't be used :/
>

I suffer for you.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231