From: "Marco Costalba" <mcostalba@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: QGit: Shrink used memory with custom git log format
Date: Tue, 27 Nov 2007 13:36:24 +0100 [thread overview]
Message-ID: <e5bfff550711270436i712d531bge5072e75285c4a4b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711271045430.27959@racer.site>
On Nov 27, 2007 11:48 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
>
> > > Indeed there is a git-rev-list --stdin option but with different
> > > behaviour from git-diff-tree --stdin and not suitable for this.
> >
> > There was a proposed patch for git-cat-file that would let you run
> > it in a --stdin mode; the git-svn folks wanted this to speed up
> > fetching raw objects from the repository. That may help as you
> > could get commit bodies (in raw format - not reencoded format!)
> > quite efficiently.
>
That would be nice.
> > Otherwise I think what you really want here is a libgit that you can
> > link into your process and that can efficiently inflate an object
> > on demand for you.
I would think libgit is overkilling for this.
You probably would not use libgit to just add a single feature but to
change completely the interface with git because the required work is
heavy both on git side and qgit side (you probably would want to run
the libgit linked part in a separated thread to avoid GUI soft locks
during slow processing, now, because the executed git command is a
different process from qgit, the OS scheduler takes care of this 'for
free').
Marco
next prev parent reply other threads:[~2007-11-27 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 8:14 QGit: Shrink used memory with custom git log format Marco Costalba
2007-11-27 1:52 ` Shawn O. Pearce
2007-11-27 10:48 ` Johannes Schindelin
2007-11-27 12:36 ` Marco Costalba [this message]
2007-11-27 19:19 ` Jan Hudec
2007-11-28 12:01 ` Johannes Schindelin
2007-11-28 15:53 ` jhud7196
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=e5bfff550711270436i712d531bge5072e75285c4a4b@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).