From: Jonathan Nieder <jrnieder@gmail.com>
To: Geert Bosch <bosch@adacore.com>
Cc: Nicolas Pitre <nico@fluxnic.net>,
Shawn Pearce <spearce@spearce.org>,
Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
Jakub Narebski <jnareb@gmail.com>,
"Dmitry S. Kravtsov" <idkravitz@gmail.com>,
git@vger.kernel.org
Subject: Narrow clone (Re: features from GitSurvey 2010)
Date: Thu, 3 Feb 2011 11:39:09 -0600 [thread overview]
Message-ID: <20110203173835.GC30341@elie> (raw)
In-Reply-To: <FE2BDD68-9CFA-4CBB-9F66-32BE6CF3E174@adacore.com>
Geert Bosch wrote:
> These narrow clones are especially important for imports of unwieldy
> svn repositories where there is a large amount of unstructured
> branching.
Wouldn't a more careful import be a better solution to that problem?
Practically speaking, I'd rather work with an enormous svn repo like
that by using git-svn to extract subsets than with a botched import
that treats it as one huge (git-managed) project.
svn-all-fast-import, for example, has a fairly simple configuration
syntax allowing to extract whatever subrepositories are needed.
next prev parent reply other threads:[~2011-02-03 17:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 10:01 Features from GitSurvey 2010 Dmitry S. Kravtsov
2011-01-29 23:13 ` Jonathan Nieder
2011-02-01 13:51 ` Jakub Narebski
2011-02-01 15:52 ` Nguyen Thai Ngoc Duy
2011-02-01 16:33 ` Shawn Pearce
2011-02-01 16:27 ` Shawn Pearce
2011-02-01 17:05 ` Nguyen Thai Ngoc Duy
2011-02-01 21:27 ` Junio C Hamano
2011-02-01 21:44 ` Nicolas Pitre
2011-02-01 17:11 ` Nguyen Thai Ngoc Duy
2011-02-01 17:34 ` Shawn Pearce
2011-02-01 21:51 ` Nicolas Pitre
2011-02-02 0:26 ` Shawn Pearce
2011-02-02 2:11 ` Nicolas Pitre
2011-02-02 2:23 ` david
2011-02-03 14:38 ` Geert Bosch
2011-02-03 17:39 ` Jonathan Nieder [this message]
2011-02-03 21:23 ` Narrow clone (Re: features from GitSurvey 2010) Geert Bosch
2011-02-03 21:33 ` Jonathan Nieder
2011-02-03 21:38 ` Jonathan Nieder
2011-02-03 21:33 ` Features from GitSurvey 2010 Nicolas Pitre
2011-02-01 17:28 ` Tracking empty directories Jonathan Nieder
2011-02-01 17:54 ` Nguyen Thai Ngoc Duy
2011-02-01 18:15 ` Ilari Liusvaara
2011-02-01 18:31 ` Jakub Narebski
2011-02-01 19:09 ` Ilari Liusvaara
2011-02-01 18:35 ` Jonathan Nieder
2011-02-01 19:03 ` Jakub Narebski
2011-02-02 3:54 ` Nguyen Thai Ngoc Duy
2011-02-02 12:31 ` Kevin P. Fleming
2011-02-01 21:36 ` Features from GitSurvey 2010 Nicolas Pitre
2011-02-01 22:50 ` big files in git was: " david
2011-02-03 6:25 ` Nicolas Pitre
2011-02-01 17:44 ` Matthieu Moy
2011-02-01 18:42 ` Jonathan Nieder
2011-02-01 20:23 ` Matthieu Moy
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=20110203173835.GC30341@elie \
--to=jrnieder@gmail.com \
--cc=bosch@adacore.com \
--cc=git@vger.kernel.org \
--cc=idkravitz@gmail.com \
--cc=jnareb@gmail.com \
--cc=nico@fluxnic.net \
--cc=pclouds@gmail.com \
--cc=spearce@spearce.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).