git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: santos2010 <santos.claudia2009@googlemail.com>
To: git@vger.kernel.org
Subject: Re: GIT Performance question
Date: Sat, 17 Apr 2010 03:21:13 -0800 (PST)	[thread overview]
Message-ID: <1271503273779-4917251.post@n2.nabble.com> (raw)
In-Reply-To: <20100417104037.GA20631@dpotapov.dyndns.org>


Thanks a lot for the quick answer. Are there some references (on-line books
or web pages) where i could find details about this approach? I need this to
justify my evaluation :)
-- 
View this message in context: http://n2.nabble.com/GIT-Performance-question-tp4917066p4917251.html
Sent from the git mailing list archive at Nabble.com.

  reply	other threads:[~2010-04-17 11:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17  9:55 GIT Performance question santos2010
2010-04-17 10:37 ` Geert Bosch
2010-04-17 10:37 ` Jeff King
2010-04-17 10:40 ` Dmitry Potapov
2010-04-17 11:21   ` santos2010 [this message]
2010-04-17 11:55     ` Jeff King

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=1271503273779-4917251.post@n2.nabble.com \
    --to=santos.claudia2009@googlemail.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).