From: "Eirik Bjørsnøs" <eirbjo@gmail.com>
To: git@vger.kernel.org
Subject: Re: Efficient retrieval of commit log info
Date: Wed, 12 Dec 2007 16:19:05 +0100 [thread overview]
Message-ID: <34660cca0712120719p2d7cda44s97ab770abd648742@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.99999.0712121001430.555@xanadu.home>
> 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:
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.
next prev parent reply other threads:[~2007-12-12 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 14:36 Efficient retrieval of commit log info Eirik Bjørsnøs
2007-12-12 14:55 ` Johannes Schindelin
2007-12-12 15:04 ` Nicolas Pitre
2007-12-12 15:19 ` Eirik Bjørsnøs [this message]
2007-12-12 15:34 ` Jon Smirl
2007-12-12 15:50 ` Eirik Bjørsnøs
2007-12-12 15:34 ` Santi Béjar
2007-12-12 16:24 ` Linus Torvalds
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=34660cca0712120719p2d7cda44s97ab770abd648742@mail.gmail.com \
--to=eirbjo@gmail.com \
--cc=git@vger.kernel.org \
/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).