From: Joshua Roys <roysjosh@gmail.com>
To: gittorrent@lists.utsl.gen.nz
Cc: Petr Baudis <pasky@suse.cz>, Jakub Narebski <jnareb@gmail.com>,
Sam Vilain <sam@vilain.net>,
git@vger.kernel.org
Subject: Re: [GSoC] What is status of Git's Google Summer of Code 2008 projects?
Date: Mon, 21 Jul 2008 09:23:27 -0400 [thread overview]
Message-ID: <48848DCF.30803@gmail.com> (raw)
In-Reply-To: <20080721104032.GI32184@machine.or.cz>
Petr Baudis wrote:
> On Mon, Jul 21, 2008 at 12:23:45PM +0200, Jakub Narebski wrote:
>> [*1*] "the current implementation is quite slow (requiring two calls to
>> 'git-cat-file' for each object)" <-- why you don't use '--batch' or
>> '--batch-check' options to git cat file: see also Git::Repo and friends
>> implementation send by Lea Wiemann to git mailing list as part of
>> "Gitweb caching" project? BTW. by keeping discussion off the list,
>> you are off the knowledge of git community, too.
>
> I concur. Only now I realized that this project might be an important
> Git Perl API user. Can you please reconsider having a separate mailing
> list for discussions etc.? The traffic seems to be very low anyway, and
> I'm not sure what benefits does it actually have at all.
>
> Petr "Pasky" Baudis
Thank you for that suggestion! I made it call cat-file only once in
batch mode and it goes quite a bit faster now.
Josh
next prev parent reply other threads:[~2008-07-21 13:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 0:27 [GSoC] What is status of Git's Google Summer of Code 2008 projects? Jakub Narebski
2008-07-08 0:43 ` David Symonds
2008-07-08 1:00 ` Stephan Beyer
2008-07-08 1:14 ` Junio C Hamano
2008-07-08 1:47 ` Stephan Beyer
2008-07-08 7:39 ` Jakub Narebski
2008-07-08 14:42 ` Stephan Beyer
2008-07-08 16:12 ` Jakub Narebski
2008-07-08 16:34 ` Stephan Beyer
2008-07-08 17:31 ` Jakub Narebski
2008-07-08 4:08 ` Lea Wiemann
2008-07-08 7:20 ` J.H.
2008-07-08 4:19 ` Shawn O. Pearce
2008-07-08 16:31 ` Joshua Roys
2008-07-08 16:45 ` Johannes Schindelin
2008-07-08 17:22 ` Jakub Narebski
2008-07-08 17:00 ` Petr Baudis
2008-07-08 21:24 ` Sam Vilain
2008-07-09 10:18 ` Sverre Rabbelier
2008-07-09 10:56 ` Miklos Vajna
2008-07-09 11:36 ` Jakub Narebski
2008-07-20 22:29 ` Jakub Narebski
2008-07-20 22:43 ` Sverre Rabbelier
2008-07-20 22:57 ` Stephan Beyer
2008-07-21 0:55 ` Sam Vilain
2008-07-21 1:05 ` Johannes Schindelin
2008-07-21 10:23 ` Jakub Narebski
2008-07-21 10:40 ` Petr Baudis
2008-07-21 13:23 ` Joshua Roys [this message]
2008-07-21 3:22 ` Shawn O. Pearce
2008-08-17 5:26 ` Sverre Rabbelier
2008-08-14 2:57 ` Jakub Narebski
2008-08-14 12:42 ` Sam Vilain
2008-08-14 23:17 ` Petr Baudis
2008-08-14 23:23 ` Jakub Narebski
2008-08-14 23:04 ` Johannes Schindelin
2008-08-15 19:38 ` Lea Wiemann
2008-08-15 20:36 ` Jakub Narebski
2008-08-16 1:16 ` Stephan Beyer
2008-08-16 1:22 ` Shawn O. Pearce
2008-08-16 3:10 ` Jakub Narebski
2008-08-17 20:49 ` Marek Zawirski
2008-08-18 5:51 ` Shawn O. Pearce
2008-08-19 1:25 ` Joshua Roys
2008-08-20 6:19 ` Sam Vilain
2008-08-22 23:03 ` Stephan Beyer
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=48848DCF.30803@gmail.com \
--to=roysjosh@gmail.com \
--cc=git@vger.kernel.org \
--cc=gittorrent@lists.utsl.gen.nz \
--cc=jnareb@gmail.com \
--cc=pasky@suse.cz \
--cc=sam@vilain.net \
/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).