Lors de l'utilisation de git svn checkout, une certaine révision de la branche est extraite à plusieurs reprises. Que dois-je faire ?

Question

Comme le montre l'exemple ci-dessous, parce que le SVN d'origine a été accidentellement supprimé et déplacé par des humains, la révision n'est pas très standardisée

Lors de l'utilisation de git svn, une révision spécifique sera constamment extraite étant donné que la plate-forme Windows utilisée a dépassé la valeur maximale du chemin du fichier, je me demande si des étudiants ont de l'expérience à cet égard.

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行

mise à jour :
L'auteur envisage de migrer de svn vers git, alors essayez de conserver l'enregistrement de la soumission

mise à jour :
L'affiche originale utilisait le paramètre --no-metadata

Answer 1

Vous pouvez ajouter --revision lors du clonage pour spécifier à partir de quelle version SVN démarrer le clonage.