Since Subversion treats branches and
Since Subversion treats branches and tags as ordinary directories, always remember to check out the trunk (http://svn.example.com/repos/calc/trunk/) of your project, and not the project itself (http://svn.example.com/repos/calc/). If you make the mistake of checking out the project itself, you'll wind up with a working copy that contains a copy of your project for every branch and tag you have.[56]
[56] That is, providing you don't run out of disk space before your checkout finishes.
| ╧Ёхф.а | ╙Ёютхэ№ т√°х | а╤ыхф. |
| Distinction Between Status and Updateа | ╤юфхЁцрэшх | аMetadata Properties |
Предупреждение, относящееся к окружающему тексту.
Обратите внимание, что примеры исходного кода являются всего лишь примерами. Хотя они и могут быть собраны с помощью определённых заклинаний для компилятора, в тексте книги они приводятся для иллюстрации соответствующей проблемы и не обязательно служат примером хорошего стиля программирования.
| Пред. | Уровень выше | След. |
| Как читать эту книгу? | Содержание | Структура книги |
You can just remove the conflict files and commit, but svn resolved fixes up some bookkeeping data in the working copy administrative area in addition to removing the conflict files, so we recommend that you use this command.
| Пред. | Уровень выше | След. |
| svn propset | Содержание | svn revert |
Be careful when using the --relocate option. If you mistype the argument, you might end up creating nonsensical URLs within your working copy that render the whole workspace unusable and tricky to fix. It's also important to understand exactly when one should or shouldn't use --relocate. Here's the rule of thumb:
- If the working copy needs to reflect a new directory within the repository, then use just svn switch.
- If the working copy still reflects the same repository directory, but the location of the repository itself has changed, then use svn switch --relocate.
| Пред. | Уровень выше | След. |
| svn status | Содержание | svn unlock |
Revision properties are not under version control, so this command will permanently overwrite the previous log message.
