You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@subversion.apache.org by "Julian Foad (Jira)" <ji...@apache.org> on 2019/11/14 16:28:00 UTC

[jira] [Assigned] (SVN-3626) Commit checkpointing

     [ https://issues.apache.org/jira/browse/SVN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Foad reassigned SVN-3626:
--------------------------------

    Assignee:     (was: Julian Foad)

> 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
>            Priority: Major
>              Labels: api, needsdesign
>             Fix For: unscheduled, 1.12.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
(v8.3.4#803005)