From: "Jörg Olschewski" <jo@bitvalve.org>
To: git@vger.kernel.org
Subject: git-svn v1 layout migration even though there was no git-svn layout
Date: Tue, 19 Jun 2012 21:43:44 +0200 [thread overview]
Message-ID: <4FE0D670.5000504@bitvalve.org> (raw)
Sometimes I accidentally try to fetch changes by doing a "git-svn fetch"
in a git repository that is not connected to any SVN repository.
Then git tells me that data from a previous version of git-svn exists,
and migrates to a new git-svn layout.
I think this is unexpected and unintended behavior and thus I consider
this to be a bug.
How to reproduce:
$ git init tmp && cd tmp && git svn fetch
Initialized empty Git repository in /home/jo/tmp/.git/
Migrating from a git-svn v1 layout...
Data from a previous version of git-svn exists, but
.git/svn
(required for this version (1.7.11) of git-svn) does not exist.
Done migrating from a git-svn v1 layout
[svn-remote "svn"] unknown
$
I would expect some output like "this is not a git-svn layout", but
maybe I miss a point here?
Best regards
Jörg
reply other threads:[~2012-06-19 19:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4FE0D670.5000504@bitvalve.org \
--to=jo@bitvalve.org \
--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).