From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: "Andy Whitcroft" <apw@shadowen.org>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Mozilla, git and Windows
Date: Mon, 27 Nov 2006 17:37:25 +0100 [thread overview]
Message-ID: <200611271737.25733.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <9e4733910611270813g4ff982b0tbe6b57d1d49ca9f7@mail.gmail.com>
måndag 27 november 2006 17:13 skrev Jon Smirl:
> On 11/27/06, Andy Whitcroft <apw@shadowen.org> wrote:
> > I think you are more likely to win letting them convert over to SVN.
> > From there people naturally start using git mirrors from the SVN trunk.
> > Cirtainly I have two projects which do not use git, one in CVS and one
> > in SVN. I just svnimport that and work in git. I am confident with
> > time the project will migrate, but I am happy other git users are happy
> > all without it being the tool of choice.
>
> The SVN version of the Mozilla repository is about 3GB. It takes
> around a week of CPU time for svnimport to process it.
You can track parts of an SVN repo using git-svn. You rarely need the
whole history to start working on a project.
In addition some nice soul with too much hardware will probably make an import
and publish it and track it so everybody won't have to. We see a lot of
git-tracked repos SVN/CVS already.
next prev parent reply other threads:[~2006-11-27 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 15:28 Mozilla, git and Windows Jon Smirl
2006-11-27 15:34 ` Andy Whitcroft
2006-11-27 16:13 ` Jon Smirl
2006-11-27 16:37 ` Robin Rosenberg [this message]
2006-11-27 22:13 ` Petr Baudis
2006-11-28 1:35 ` Jon Smirl
2006-11-28 12:17 ` Michael Haggerty
2006-11-28 0:30 ` Sam Vilain
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=200611271737.25733.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=apw@shadowen.org \
--cc=git@vger.kernel.org \
--cc=jonsmirl@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 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).