Closed lee-davidson closed 6 years ago
Thanks for reporting it, but it sounds more like an issue with deleting the git repository than with vss2git. Also, it would need detailed reproduction steps to be actionable. I'm closing this for now, but feel free to reopen if you can demonstrate how to reproduce the issue and vss2git appears to be the cause.
That's fine. This may well be Git's fault. If I have time I might experiment a bit, but you can close the issue certainly.
On Thu, Jul 19, 2018 at 12:24 PM, Trevor Robinson notifications@github.com wrote:
Thanks for reporting it, but it sounds more like an issue with deleting the git repository than with vss2git. Also, it would need detailed reproduction steps to be actionable. I'm closing this for now, but feel free to reopen if you can demonstrate how to reproduce the issue and vss2git appears to be the cause.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/trevorr/vss2git/issues/49#issuecomment-406387159, or mute the thread https://github.com/notifications/unsubscribe-auth/AnY2ubLSv9GH_Y8afsj1-bxTM3PvIIgcks5uINz0gaJpZM4VRmkE .
I downloaded, built, and ran vss2git successfully last week. Today I needed to run it again. I cleaned out the Git directory, ran it again, and it complained when it first tried to create the very first tag that the tag already exists.
I just hacked around: got rid of the target git directory completely, got rid of a clone, and rebuilt vss2git in Visual Studio. Now it worked fine. There must have been, somehow, some scraps of data left over someplace, but apparently I got rid of them. Anyway, this is a possible issue.