Problems with git-svnimport

Problems with git-svnimport

[Alex R.M. Turner]

I am trying to import my svn project into git with git-svnimport, but I am 
getting a bunch of error messages using the following command:

git-svnimport -C eastcoastmarine -v \
svn://svn.mintpixels.com/eastcoastmarine-website

I get messages like:
4: Unrecognized path: /trend-scripts/trunk/run_purge.sh

Is this expected, or should I be worried?

Alex

Re: Problems with git-svnimport

[Johannes Schindelin]

Hi,

On Thu, 7 Jun 2007, Alex R.M. Turner wrote:

> I am trying to import my svn project into git with git-svnimport, but I am 
> getting a bunch of error messages using the following command:
> 
> git-svnimport -C eastcoastmarine -v \
> svn://svn.mintpixels.com/eastcoastmarine-website
> 
> I get messages like:
> 4: Unrecognized path: /trend-scripts/trunk/run_purge.sh

Let's deprecate git-svnimport, once for all.

git-svn should work much better.

Ciao,
Dscho

Re: Problems with git-svnimport

[Martin Langhoff]

On 6/8/07, Alex R.M. Turner <aturner@plexq.com> wrote:
> Is this expected, or should I be worried?

It means that  you need to play a bit with your import settings. It
usually takes me a few tried to get the right trunk, tags and branches
parameter for each repo. SVN's layout is a bit too flexible and
doesn't make this easy to figure out.

cheers,


martin

Re: Problems with git-svnimport

[Matthias Urlichs]

Johannes Schindelin <Johannes.Schindelin <at> gmx.de> writes:

> Let's deprecate git-svnimport, once for all.
> 
> git-svn should work much better.
> 
In other words, you volunteer to fold everything that git-svnimport can do into
git-svn? The last time I checked, neither was a feature-complete subset of the
other...

If so: don't let me hold you back. ;-)

-- 
Matthias Urlichs

Re: Problems with git-svnimport

[Peter Baumann]

On Tue, Jul 03, 2007 at 07:45:12PM +0000, Matthias Urlichs wrote:
> Johannes Schindelin <Johannes.Schindelin <at> gmx.de> writes:
> 
> > Let's deprecate git-svnimport, once for all.
> > 
> > git-svn should work much better.
> > 
> In other words, you volunteer to fold everything that git-svnimport can do into
> git-svn? The last time I checked, neither was a feature-complete subset of the
> other...
> 
> If so: don't let me hold you back. ;-)
> 

May I ask what is missing in git-svn to replace git-svnimport? As I
can't think of anything which is missing in git-svn.

-Peter