En subversión la definición de changeset es mas concreta:
A changeset is just a collection of changes with a unique name. The changes might include
In more common speak, a changeset is just a patch with a name you can refer to.
In Subversion, a global revision number
Nnames a tree in the repository: it's the way the repository looked after the
Nth commit. It's also the name of an implicit changeset: if you compare tree
N−1, you can derive the exact patch that was committed. For this reason, it's easy to think of revision
Nas not just a tree, but a changeset as well.
If you use an issue tracker to manage bugs, you can use the revision numbers to refer to particular patches that fix bugs—for example, 'this issue was fixed by
r9238.' Somebody can then run
svn log -r 9238
to read about the exact changeset that fixed the bug, and run
svn diff -c 9238 # La opción -c REV es equivalente a -r REV-1:REV
to see the patch itself.
svn mergecommand is able to use revision numbers. You can merge specific changesets from one branch to another by naming them in the merge arguments: passing
svn mergewould merge changeset
r9238into your working copy.
Casiano Rodríguez León