[
https://issues.apache.org/jira/browse/SVN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625788#comment-16625788
]
Julian Foad commented on SVN-3626:
----------------------------------
Going in to 1.11, the [Release
Notes|http://subversion.apache.org/docs/release-notes/1.11.html] describe the
present implementation as follows.
{quote}Subversion 1.11 provides an experimental first cut at solving some of
the use cases envisioned in issue #3626 named "Commit checkpointing".
It provides the ability to save a snapshot of an uncommitted change from time
to time, and later restore one of those previous versions of your change back
into the working copy.
It does not provide the kind of exact WC state roll back that is also discussed
in that issue, that could make it possible after a messy update to roll back to
the exact WC state that existed just before. This remains a future possibility.
The ability to checkpoint and roll back an uncommitted change is provided
within the shelving feature, by letting a shelf hold multiple versions of your
change. Therefore, see also
[Shelving|http://subversion.apache.org/docs/release-notes/1.11.html#shelving].
{quote}
> 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.0
>
> Attachments: 20171228-J-TSVN-ShelveCheckptDlg2.pdf,
> 20180105-J-TSVN-ShelfChooserDlg1.pdf, 20180105-J-TSVN-UnshelveDlg2.pdf,
> 20180111-J-TSVN-UnshelveDlg3.pdf
>
>
> (i) See the wiki pages: [Shelving and
> Checkpointing|https://cwiki.apache.org/confluence/display/SVN/Shelving+and+Checkpointing]
> 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)
