Re: Efficient retrieval of commit log info

From: Jon Smirl <jonsmirl@gmail.com>
Date: Dec 12, 2007, 15:34 UTC
Message-ID: <9e4733910712120734r2618e882w1e6f930c74f3065a@mail.gmail.com>
In-Reply-To: <34660cca0712120719p2d7cda44s97ab770abd648742@mail.gmail.com>

On 12/12/07, Eirik Bjørsnøs <eirbjo@gmail.com> wrote:

Show 7 quoted lines

> > On the other hand, this is pretty trivial to extend the protocol so only
> > commit objects are transferred.  Using 'git log' on the client side
> > would work, as long as you don't use any of the content walking options.
>
> Nicolas,
>
> So what you're suggesting is that:

Write a script the runs the command locally on the remote sever and emails you the info. Or ssh to the remote server and run the commands locally.

Show 17 quoted lines

>
> 1) git-clone could be changed such that the user could ask not to
> fetch content, only commit objects.
> 2) git-daemon (or the protocol layer, again I'm not familiar with the
> implementation) could be changed such that it only sends commit
> objects on request.
> 3) Changes to git-log is not necessary.
>
> Anybody have a clue how much work this would require and if this is
> something that would be generally useful for the community?
>
> Eirik.
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

-- 
Jon Smirl
jonsmirl@gmail.com