[
https://issues.apache.org/jira/browse/SVN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214745#comment-16214745
]
Julian Foad commented on SVN-3626:
----------------------------------
I am working on Shelving and Checkpointing, as it is a component of Assembla's
[Enterprise Cloud Version Control|https://www.assembla.com/ecvc].
* discussing in dev@ threads, initially "[\[RFC\] Shelving and
Checkpointing|https://lists.apache.org/thread.html/4fe683f50f4528e3b6e4a66ceffedc673622e82a5f3587083c77384a@%3Cdev.subversion.apache.org%3E]";
* designing in the document "[Shelving-Checkpointing
Dev|https://docs.google.com/document/d/1PVgw0BdPF7v67oxIK7B_Yjmr3p28ojabP5N1PfZTsHk/]";
* prototyping in the
"[shelve-checkpoint|http://svn.apache.org/repos/asf/subversion/branches/shelve-checkpoint/]";
&
"[shelve-checkpoint3|http://svn.apache.org/repos/asf/subversion/branches/shelve-checkpoint3/]";
branches
> 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)
