From: Hans-Juergen Euler <waas.nett@gmail.com>
To: git@vger.kernel.org
Subject: git-svn problems with white-space in tag names
Date: Wed, 23 Jan 2013 11:23:42 +0100 [thread overview]
Message-ID: <CAK3CF+4GPKBfAmgsHYnf_6nCCOCe-1d31cGsWp4jkKC28cZr0g@mail.gmail.com> (raw)
I have discussed already the problem a bit more in this thread
groups.google.com/d/topic/git-users/kfMFZ3uEFsM/discussion
-----Operating system (specifically which version)
windows 7 64 bit
------Git version (git --version)
Git version 1.8.0 for windows obviously.
git bash and git gui installed and using
------Git configuration (system, home, repository)
hmm guess is covered with git bash and git gui. Using the standard config stuff
using subversion
TortoiseSVN 1.7.11
Subversion 1.7.8
Was typically always up-to-date (within 2 months or so) with previous versions
using an external subversion provider for storing the information
externally. guess the version there is older but do not know
I have tried to convert some of my external subversion data bases with
git-svn clone
I have encountered a problem with one of my subversion repos. I have
obviously introduced about 2 years ago a problem with an additional
white space at the end of tag name.
So there is an entry "tags/blabla "
in the subversion repos. The sequential handling of the svn repos with
git-svn gets stuck there. I could not find a way around this. My guess
is that the white-space was introduced by accident on windows by
Tortoise-SVN.
Unfortunately this occurs at revision 90 something and I have almost
1000 revisions stored.
Let me know if you need more details.Thanks.
next reply other threads:[~2013-01-23 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 10:23 Hans-Juergen Euler [this message]
2013-01-27 14:12 ` git-svn problems with white-space in tag names Hans-Juergen Euler
2013-02-06 9:26 ` Erik Faye-Lund
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=CAK3CF+4GPKBfAmgsHYnf_6nCCOCe-1d31cGsWp4jkKC28cZr0g@mail.gmail.com \
--to=waas.nett@gmail.com \
--cc=git@vger.kernel.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).