From: Thomas Rast <trast@student.ethz.ch>
To: Subho Banerjee <subs.zero@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: GSoC Application [ Parallelism + Git.pm ]
Date: Wed, 21 Mar 2012 13:47:26 +0100 [thread overview]
Message-ID: <871uomt929.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <CAB3zAY1cbjmJvPQo2i38Vxv=1CTzcusvtBTPQehi30cYsDe1Zw@mail.gmail.com> (Subho Banerjee's message of "Sun, 18 Mar 2012 13:06:17 +0530")
Subho Banerjee <subs.zero@gmail.com> writes:
> * In the first one, which wants to parallelize certain commands in
> git, I believe the major challenges will be to actually find a large
> list of commands which can be parallelized.In addition to the commands
> mentioned in the Ideas page, only other place I currently think of
> exploiting parallelism is in traversing the commit tree when one is
> cloning a repository. I would really like it if someone can suggest
> more places where this sort of parallelism might be usable, so that I
> could use that to make a more complete application. I believe one of
> the major difficulties I will initially face, is my unfamiliarity with
> the code. This makes finding these commands which might have better
> performance with parallelism a little difficult.
Please read my reply to Felipe in the other thread:
http://thread.gmane.org/gmane.comp.version-control.git/193352/focus=193574
as I'd have to repeat myself.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-03-21 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 7:36 GSoC Application [ Parallelism + Git.pm ] Subho Banerjee
2012-03-18 16:31 ` Jakub Narebski
2012-03-21 18:52 ` Subho Banerjee
2012-03-22 13:33 ` Jakub Narebski
2012-03-21 12:47 ` Thomas Rast [this message]
2012-03-21 13:53 ` Subho Banerjee
2012-03-21 14:10 ` Nguyen Thai Ngoc Duy
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=871uomt929.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=subs.zero@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.