Open GoogleCodeExporter opened 9 years ago
Original comment by chrsm...@google.com
on 14 Mar 2015 at 10:58
I really do not agree with the classification that this as an enhancement. This
is a bug in my opinion.
As it currently works projects are not migrated properly due to the GitHub
abuse filter or any other issue occurring while the migration is in progress.
Will the current script work if I remove the comments completely from GitHub? I
do not think I can remove the issue itself.
Original comment by hans.bec...@gmail.com
on 15 Mar 2015 at 1:42
@hans.beckerus: Until this issue is resolved, you can always delete the GitHub
repo and retry importing from the beginning. Since there's a workaround (albeit
an inconvenient one), this is an Enhancement.
Original comment by jasonhall@google.com
on 16 Mar 2015 at 8:50
That workaround is not applicable in my use case. I have had the code
duplicated in SVN and GIT for a very long time. Deleting the repo, and import
from scratch, would throw away all history and commit ids. Thus, this is a bug
and not an enhancement. Sorry, but to me it is obviously a bug if a tool can
not seamlessly handle a break during the migration. Prioritization is something
different though. But I would really like to see some priority on this one.
Original comment by hans.bec...@gmail.com
on 17 Mar 2015 at 7:33
Original issue reported on code.google.com by
hans.bec...@gmail.com
on 13 Mar 2015 at 12:10