From: "Eirik Bjørsnøs" <eirbjo@gmail.com>
To: git@vger.kernel.org
Subject: Efficient retrieval of commit log info
Date: Wed, 12 Dec 2007 15:36:15 +0100 [thread overview]
Message-ID: <34660cca0712120636w149e2a82h84609f8ac7c958a9@mail.gmail.com> (raw)
Hi,
I'm developing a piece of software that grabs logs from various types
of SCMs and presents (hopefully) useful information about the history.
My current approach with Git is do a "git clone --n" and then parse
the output of "git log". To check for updates I do a "git pull"
followed by a new "git log".
This approach works fine, but cloning the whole repository just to get
the change log seems like a somewhat inefficient use of bandwidth and
storage.
What I would like to do is to fetch just the change log information
from the remote repository.
(Using the "CVS done right" tool I can do this with: "svn log --xml -v
-r<last, HEAD> http://svn.example.com/")
I haven't found a way to do this using the Git command line tools.
Is it at all possible using the git network protocols to fetch just
the commit log info, without transferring the contents?
I'd be happy to hear from anyone who has some insight into this.
Thanks,
Eirik.
next reply other threads:[~2007-12-12 14:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 14:36 Eirik Bjørsnøs [this message]
2007-12-12 14:55 ` Efficient retrieval of commit log info Johannes Schindelin
2007-12-12 15:04 ` Nicolas Pitre
2007-12-12 15:19 ` Eirik Bjørsnøs
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=34660cca0712120636w149e2a82h84609f8ac7c958a9@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).