From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Eirik Bjørsnøs" <eirbjo@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Efficient retrieval of commit log info
Date: Wed, 12 Dec 2007 14:55:41 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0712121453150.27959@racer.site> (raw)
In-Reply-To: <34660cca0712120636w149e2a82h84609f8ac7c958a9@mail.gmail.com>
Hi,
On Wed, 12 Dec 2007, Eirik Bj?rsn?s wrote:
> 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.
It is not possible to get just the metadata. Remember, svn can do it only
since the repository is purely remote. And git is a SCM (source code
management system), not a CMV (commit metadata viewer).
You might be able to cobble up something that works accessing gitweb, but
it might be even more inefficient.
Ciao,
Dscho
next prev parent reply other threads:[~2007-12-12 14:56 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 [this message]
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=Pine.LNX.4.64.0712121453150.27959@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=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).