[
https://issues.apache.org/jira/browse/SVN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520365#comment-16520365
]
Julian Foad commented on SVN-3626:
----------------------------------
git uses the term "stash"
Perforce, Mercurial, Bazaar, NetBeans IDE, IntelliJ IDEA all use the term
"shelve"
See [Shelving Command-Line UI
Design|https://cwiki.apache.org/confluence/x/iZjLB]
> 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
>
>
> (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)
