As shown in the example below, because the original SVN was accidentally deleted and moved by humans, the revision is not very standardized
When using git svn, a specific revision will be constantly checked out. Since the Windows platform used has exceeded the maximum value of the file path, checkout cannot be smooth. I wonder if any students have experience in this regard. ?
refs/remotes/origin/Some_Branch@21
refs/remotes/origin/Some_Branch@21-
refs/remotes/origin/Some_Branch@21--
refs/remotes/origin/Some_Branch@21---
refs/remotes/origin/Some_Branch@21----
refs/remotes/origin/Some_Branch@21-----
refs/remotes/origin/Some_Branch@21------
refs/remotes/origin/Some_Branch@21-------
refs/remotes/origin/Some_Branch@21--------
refs/remotes/origin/Some_Branch@21---------
refs/remotes/origin/Some_Branch@21----------
refs/remotes/origin/Some_Branch@21-----------
refs/remotes/origin/Some_Branch@21------------
refs/remotes/origin/Some_Branch@21-------------
refs/remotes/origin/Some_Branch@21--------------
refs/remotes/origin/Some_Branch@21---------------
refs/remotes/origin/Some_Branch@21----------------
refs/remotes/origin/Some_Branch@21-----------------
refs/remotes/origin/Some_Branch@21------------------
refs/remotes/origin/Some_Branch@21-------------------
refs/remotes/origin/Some_Branch@21--------------------
refs/remotes/origin/Some_Branch@21---------------------
refs/remotes/origin/Some_Branch@21----------------------
refs/remotes/origin/Some_Branch@21-----------------------
refs/remotes/origin/Some_Branch@21------------------------
refs/remotes/origin/Some_Branch@21-------------------------
refs/remotes/origin/Some_Branch@21--------------------------
refs/remotes/origin/Some_Branch@21---------------------------
refs/remotes/origin/Some_Branch@21----------------------------
refs/remotes/origin/Some_Branch@21-----------------------------
refs/remotes/origin/Some_Branch@21------------------------------
refs/remotes/origin/Some_Branch@21-------------------------------
refs/remotes/origin/Some_Branch@21--------------------------------
refs/remotes/origin/Some_Branch@21---------------------------------
refs/remotes/origin/Some_Branch@21----------------------------------
refs/remotes/origin/Some_Branch@21-----------------------------------
refs/remotes/origin/Some_Branch@21------------------------------------
refs/remotes/origin/Some_Branch@21-------------------------------------
refs/remotes/origin/Some_Branch@21--------------------------------------
refs/remotes/origin/Some_Branch@21---------------------------------------
refs/remotes/origin/Some_Branch@21----------------------------------------
refs/remotes/origin/Some_Branch@21-----------------------------------------
refs/remotes/origin/Some_Branch@21------------------------------------------
refs/remotes/origin/Some_Branch@21-------------------------------------------
refs/remotes/origin/Some_Branch@21--------------------------------------------
refs/remotes/origin/Some_Branch@21---------------------------------------------
refs/remotes/origin/Some_Branch@21----------------------------------------------
refs/remotes/origin/Some_Branch@21-----------------------------------------------
...省略N行
update:
The author is considering migrating from svn to git, so try to keep the submission record
update:
The author used the --no-metadata parameter
给我你的怀抱2017-05-02 09:28:11
You can add --revision when cloning to specify which svn version to start cloning from.