What will be Subversion equivalent to TFS racks?

Question

We are moving from TFS to Subversion. A colleague noted that he would be very disappointed if he lost the ability to make racks. In TFS, you can create a set of files to save under one name. Files are saved in the repository, but not in HEAD or in any branch. Changes are simply archived and tagged.

This is similar to flagging a set of changes in Subversion, but does not require changes that need to be checked. Shelves are useful for code reviews, for creating breakpoints for stable versions of changes (not yet verified), and for easy storage of changes in the repository, even if they are not yet ready for verification.

It seems to me that for this, Subversion requires branching the code in the repository and checking one code for this branch. This is very worrying if you are likely to discard the changes.

Answer 1

Subversion has a function similar to the idea of ​​shelves. It is called Patching. See this article for a comparison of the TFS shelf and the SVN patch:

Modeling TFS Tiles in Subversion