tags 524306 + upstream retitle 524306 git svn: follow redirects severity 524306 wishlist
Hi Josef, Josef Spillner wrote: > When checking out an SVN repository which gives a HTTP 301 (Moved > Permanently), svn doesn't follow the redirect but rather requires > the user to do so manually and quite with exit code 1: [...] > Now, when checking out the same repository using git-svn, an empty > repository is created, but then git-svn recognises the same issue > and quits without cleaning up the unusable git repo: [...] > $ LANG=C git svn clone https://remotefoo/ localfoo > svn-remote.svn.url already set: http://remotefoo > wanted to set to: https://remotefoo I see a few bugs here: 1. Sometimes I want to just throw all the git svn metadata away and start over. I can: just delete the .git/svn directory, edit .git/config, and I’m done. Since the git-svn(1) man page does not explain it, how is anyone supposed to know that? 2. The error message when there is stale metadata around is bordering on useless. 3. The little amount of stale metadata from a ‘git svn clone’ failing very early is not useful. git svn should just delete it. 4. An incomplete ‘git svn clone’ leaves the repository in an “ugly” state. Probably if there are no revisions fetched, it should be as though the user did not give any command at all; if there are only a few revisions fetched, it should be as though the user ran ‘git svn clone’ earlier in the project’s history; and so on. Unfortunately, there is some up-front work that is done before a single revision gets fetched, so this one requires a little more thinking. 5. git svn does not follow redirects. #5 is easy to characterize and I think a motivated person should not find it hard to fix. So I’m going to pretend you asked for that. ;-) Work on any of the others would be welcome, too. Regards, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
