[
https://issues.apache.org/jira/browse/SVN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Foad updated SVN-3626:
-----------------------------
Description:
When working on a collection of local changes, it is sometimes desirable to be
able to checkpoint your work. The utility, of course, it not in the
checkpointing, but in the fact that you can then restore the working copy to
one of your previous checkpoints. Workarounds today generally come in the form
of temporary branches (which aren't offline) or series of patchfiles.
Subversion should offer a first-class feature to facilitate this use case.
was:
{noformat:nopanel=true}
When working on a collection of local changes, it is sometimes desirable to be
able to checkpoint your work. The utility, of course, it not in the
checkpointing, but in the fact that you can then restore the working copy to one
of your previous checkpoints. Workarounds today generally come in the form of
temporary branches (which aren't offline) or series of patchfiles. Subversion
should offer a first-class feature to facilitate this use case.
{noformat}
> Commit checkpointing
> --------------------
>
> Key: SVN-3626
> URL: https://issues.apache.org/jira/browse/SVN-3626
> Project: Subversion
> Issue Type: New Feature
> Components: libsvn_client
> Affects Versions: trunk
> Reporter: C. Michael Pilato
> Assignee: Julian Foad
> Labels: api, needsdesign
> Fix For: 1.10-consider
>
>
> When working on a collection of local changes, it is sometimes desirable to
> be able to checkpoint your work. The utility, of course, it not in the
> checkpointing, but in the fact that you can then restore the working copy to
> one of your previous checkpoints. Workarounds today generally come in the
> form of temporary branches (which aren't offline) or series of patchfiles.
> Subversion should offer a first-class feature to facilitate this use case.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
