From: <dag@cray.com>
To: Ben Tebulin <nntp.20.jexpert@spamgourmet.com>
Cc: <git@vger.kernel.org>
Subject: Re: git-svn: --ignore-paths appears to be ignored
Date: Thu, 24 May 2012 11:23:36 -0500 [thread overview]
Message-ID: <nngsjepwnsn.fsf@transit.us.cray.com> (raw)
In-Reply-To: <jpl70m$r97$1@dough.gmane.org> (Ben Tebulin's message of "Thu, 24 May 2012 13:45:33 +0200")
Ben Tebulin <nntp.20.jexpert@spamgourmet.com> writes:
> Am 07.05.2012 00:42, schrieb Jon Seymour:
>> I configured ignore-paths as follows:
>> svn-remote.svn.ignore-paths=^DB.*
>>
>> I expected this would exclude paths of this kind on the initial fetch:
>> DB/.project
>
> I have the same issue here. I'm failing to import multiple svn
> repository into Git and --ignore-paths provides me no cure.
One thing to be aware of is that --ignore-paths doesn't work across svn
branches. I tried to ignore entire branches using it and it didn't
work. I had to resort to importing chunks of revisions at a time,
skipping the ones that created and merged branches I didn't care about.
-Dave
prev parent reply other threads:[~2012-05-24 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 22:42 git-svn: --ignore-paths appears to be ignored Jon Seymour
2012-05-24 11:45 ` Ben Tebulin
2012-05-24 16:23 ` dag [this message]
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=nngsjepwnsn.fsf@transit.us.cray.com \
--to=dag@cray.com \
--cc=git@vger.kernel.org \
--cc=nntp.20.jexpert@spamgourmet.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 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.