Svn relocate что это
Рисунок 4.68. Диалог перебазирования
Если у вашего хранилища по каким-то причинам изменилось размещение (IP/URL). Возможно у вас застопорилась работа и не можете пока фиксировать, и при этом не хотите извлекать рабочую копию заново из нового размещения и затем перемещать все изменения в новую рабочую копию, команда TortoiseSVN → Перебазировать то что вам нужно. Она делает очень простую вещь: переписывает все адреса URL для каждого файла и папки новым адресом URL.
Примечание
Эта операция работает только в корне рабочей копии. Так что пункт в контекстном меню показывается только в корнях рабочих копий.
Предупреждение
Был изменён IP-адрес сервера.
Был изменён протокол (например, с http:// на https://).
Был изменён путь к корню хранилища в настройках сервера.
Другими словами, перебазирование необходимо, когда ваша рабочая копия ссылается на то же место в том же хранилище, но само хранилище было перемещено.
Перебазирование не применимо, если:
Вы желаете перейти к другому хранилищу Subversion. В этом случае вы должны выполнить извлечение заново из нового местоположения хранилища.
Если вы применили перебазирование в любом из вышеперечисленных случаев, ваша рабочая копия будет повреждена и вы получите множество необъяснимых сообщений об ошибках при обновлении, фиксации, и т.д. После того, как это случилось, единственным решением будет выполнение свежего извлечения.
Svn relocate что это
svn relocate FROM-PREFIX TO-PREFIX [PATH. ]
svn relocate TO-URL [PATH]
Description
Sometimes an administrator might change the location (or apparent location, from the client’s perspective) of a repository. The content of the repository doesn’t change, but the repository’s root URL does. The hostname may change because the repository is now being served from a different computer. Or, perhaps the URL scheme changes because the repository is now being served via SSL (using https:// ) instead of over plain HTTP. There are many different reasons for these types of repository relocations. But ideally, a “ change of address ” for a repository shouldn’t suddently cause all the working copies which point to that repository to become forever unusable. And fortunately, that’s not the case. Rather than force users to check out a new working copy when a repository is relocated, Subversion provides the svn relocate command, which “ rewrites ” the working copy’s administrative metadata to refer to the new repository location.
The first svn relocate syntax allows you to update one or more working copies by what essentially amounts to a find-and-replace within the repository root URLs recorded in those working copies. Subversion will replace the initial substring FROM-PREFIX with the string TO-PREFIX in those URLs. These initial URL substrings can be as long or as short as is necessary to differentiate between them. Obviously, to use this syntax form, you need to know both the current root URL of the repository to which the working copy is pointing, and the new URL of that repository. (You can use svn info to determine the former.)
The second syntax does not require that you know the current repository root URL with which the working copy is associated at all—only the new repository URL ( TO-URL ) to which it should be pointing. In this syntax form, only one working copy may be relocated at a time.
svn relocate
svn relocate — Relocate the working copy to point to a different repository root URL.
Synopsis
svn relocate FROM-PREFIX TO-PREFIX [PATH. ]
svn relocate TO-URL [PATH]
Description
Sometimes an administrator might change the location (or apparent location, from the client’s perspective) of a repository. The content of the repository doesn’t change, but the repository’s root URL does. The hostname may change because the repository is now being served from a different computer. Or, perhaps the URL scheme changes because the repository is now being served via SSL (using https:// ) instead of over plain HTTP. There are many different reasons for these types of repository relocations. But ideally, a “ change of address ” for a repository shouldn’t suddently cause all the working copies which point to that repository to become forever unusable. And fortunately, that’s not the case. Rather than force users to check out a new working copy when a repository is relocated, Subversion provides the svn relocate command, which “ rewrites ” the working copy’s administrative metadata to refer to the new repository location.
The first svn relocate syntax allows you to update one or more working copies by what essentially amounts to a find-and-replace within the repository root URLs recorded in those working copies. Subversion will replace the initial substring FROM-PREFIX with the string TO-PREFIX in those URLs. These initial URL substrings can be as long or as short as is necessary to differentiate between them. Obviously, to use this syntax form, you need to know both the current root URL of the repository to which the working copy is pointing, and the new URL of that repository. (You can use svn info to determine the former.)
The second syntax does not require that you know the current repository root URL with which the working copy is associated at all—only the new repository URL ( TO-URL ) to which it should be pointing. In this syntax form, only one working copy may be relocated at a time.
Svn relocate что это
Figure 4.69. The Relocate Dialog
If your repository has for some reason changed it’s location (IP/URL). Maybe you’re even stuck and can’t commit and you don’t want to checkout your working copy again from the new location and to move all your changed data back into the new working copy, TortoiseSVN → Relocate is the command you are looking for. It basically does very little: it rewrites all URLs that are associated with each file and folder with the new URL.
You may be surprised to find that TortoiseSVN contacts the repository as part of this operation. All it is doing is performing some simple checks to make sure that the new URL really does refer to the same repository as the existing working copy.
Warning
The IP address of the server has changed.
The protocol has changed (e.g. http:// to https://).
The repository root path in the server setup has changed.
Put another way, you need to relocate when your working copy is referring to the same location in the same repository, but the repository itself has moved.
It does not apply if:
You want to move to a different Subversion repository. In that case you should perform a clean checkout from the new repository location.
If you use relocate in either of the cases above, it will corrupt your working copy and you will get many unexplainable error messages while updating, committing, etc. Once that has happened, the only fix is a fresh checkout.
Svn relocate что это
svn relocate FROM-PREFIX TO-PREFIX [PATH. ]
svn relocate TO-URL [PATH]
Description
Sometimes an administrator might change the location (or apparent location, from the client’s perspective) of a repository. The content of the repository doesn’t change, but the repository’s root URL does. The hostname may change because the repository is now being served from a different computer. Or, perhaps the URL scheme changes because the repository is now being served via SSL (using https:// ) instead of over plain HTTP. There are many different reasons for these types of repository relocations. But ideally, a “ change of address ” for a repository shouldn’t suddently cause all the working copies which point to that repository to become forever unusable. And fortunately, that’s not the case. Rather than force users to check out a new working copy when a repository is relocated, Subversion provides the svn relocate command, which “ rewrites ” the working copy’s administrative metadata to refer to the new repository location.
The first svn relocate syntax allows you to update one or more working copies by what essentially amounts to a find-and-replace within the repository root URLs recorded in those working copies. Subversion will replace the initial substring FROM-PREFIX with the string TO-PREFIX in those URLs. These initial URL substrings can be as long or as short as is necessary to differentiate between them. Obviously, to use this syntax form, you need to know both the current root URL of the repository to which the working copy is pointing, and the new URL of that repository. (You can use svn info to determine the former.)
The second syntax does not require that you know the current repository root URL with which the working copy is associated at all—only the new repository URL ( TO-URL ) to which it should be pointing. In this syntax form, only one working copy may be relocated at a time.