[
https://issues.apache.org/jira/browse/SVN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335649#comment-16335649
]
Julian Foad commented on SVN-3626:
----------------------------------
Checkpointing v1 is now in Subversion trunk. It works as versions of a 'shelf'.
The set of shelving commands is now:
shelf-diff NAME [VERSION]
shelf-drop NAME
shelf-list (shelves)
shelf-log NAME
shelf-save NAME [PATH...]
shelve [--keep-local] NAME [PATH...]
unshelve [NAME [VERSION]]
The checkpointing part works like this: both 'shelf-save' and 'shelve' store a
new version of the shelf; 'unshelve' retrieves the newest version by default
and an old version if specified.
> 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
> Priority: Major
> Labels: api, needsdesign
> Fix For: 1.11-consider
>
> Attachments: 20171228-J-TSVN-ShelveCheckptDlg2.pdf,
> 20180105-J-TSVN-ShelfChooserDlg1.pdf, 20180105-J-TSVN-UnshelveDlg2.pdf,
> 20180111-J-TSVN-UnshelveDlg3.pdf
>
>
> 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
(v7.6.3#76005)
