git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Khapyorsky <sashak@voltaire.com>
To: Karl Hasselstr?m <kha@treskal.com>
Cc: Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org, Matthias Urlichs <smurf@smurf.noris.de>
Subject: Re: [PATCH] git-svnimport: support for partial imports
Date: Thu, 26 Oct 2006 12:31:20 +0200	[thread overview]
Message-ID: <20061026103120.GA15502@sashak.voltaire.com> (raw)
In-Reply-To: <20061026084710.GC13780@diana.vm.bytemark.co.uk>

On 10:47 Thu 26 Oct     , Karl Hasselstr?m wrote:
> On 2006-10-26 00:50:26 +0200, Sasha Khapyorsky wrote:
> 
> > This adds support for partial svn imports. Let's assume that SVN
> > repository layout looks like:
> >
> >   $trunk/path/to/our/project
> >   $branches/path/to/our/project
> >   $tags/path/to/our/project
> >
> > , and we would like to import only tree under this specific
> > 'path/to/our/project' and not whole tree under $trunk, $branches,
> > etc.. Now we will be be able to do it by using '-P
> > path/to/our/project' option with git-svnimport.
> 
> Isn't this already doable with "-T trunk/path/to/our/project -t
> tags/path/to/our/project -b branches/path/to/our/project"?

In such case git-svnimport will not be able to resolve branches and
tags names - note that actual SVN paths are:

  branches/<branch-name>/path/to/our/project
  tags/<tag-name>/path/to/our/project


  reply	other threads:[~2006-10-26 10:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 22:50 [PATCH] git-svnimport: support for partial imports Sasha Khapyorsky
2006-10-26  8:47 ` Karl Hasselström
2006-10-26 10:31   ` Sasha Khapyorsky [this message]
2006-10-26 10:54     ` Karl Hasselström
2006-10-31 22:50 ` Sasha Khapyorsky
2006-10-31 23:48   ` Junio C Hamano
2006-11-01  0:51     ` Sasha Khapyorsky

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=20061026103120.GA15502@sashak.voltaire.com \
    --to=sashak@voltaire.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=kha@treskal.com \
    --cc=smurf@smurf.noris.de \
    /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).