All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaud Bailly <abailly@oqube.com>
To: git@vger.kernel.org
Subject: From P4 to Git
Date: Tue, 28 Jul 2009 22:14:34 +0200	[thread overview]
Message-ID: <85ljm84lat.fsf@oqube.com> (raw)

Hello,
I am investigating the use of Git in a setting where we:
 1. branches a lot
 2. have a very large codebase

Given Git is developed to handle these 2 issues, I suspect it would be a
very good choice, but I need to gather some experiments feedback and
hard figures on how Git performs (storage use, necessary
bandwidth/resources, maintainance of repositories, cleanup & gc...).

For the experiment part, I am started working on it but would be
interested in other people's experiences.

For the figures part, I think I read somewhere there exists some
statistics on Git usage for Linux kernel. Is this correct ? If true,
where could I find them ? 

Thanks in advance for answering my (maybe pointless) questions and for
producing such a nice piece of software.
-- 
Arnaud Bailly

             reply	other threads:[~2009-07-28 20:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28 20:14 Arnaud Bailly [this message]
2009-07-28 20:32 ` From P4 to Git david
2009-07-28 21:10 ` Jakub Narebski
     [not found]   ` <85r5vxbd8e.fsf@oqube.com>
2009-07-31  9:22     ` Jakub Narebski
2009-07-31 11:14       ` Alex Riesen
2009-08-03  7:49         ` Sam Vilain
2009-08-03  8:47           ` Alex Riesen
2009-08-03 11:30             ` Sam Vilain
2009-08-03 13:50               ` Alex Riesen
2009-08-03 20:32                 ` Sam Vilain
2009-08-03 21:51                   ` Alex Riesen
2009-08-04  0:29                     ` Sam Vilain
2009-08-02  7:16       ` Sam Vilain
2009-08-04 12:31       ` Arnaud Bailly
2009-08-04 12:35         ` Peter Baumann
2009-08-03 21:37   ` John Tapsell

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=85ljm84lat.fsf@oqube.com \
    --to=abailly@oqube.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 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.