[jira] [Commented] (SVN-4786) Create a WC working-mods editor
"Julian Foad (JIRA)" <[email protected]>
| Newsgroups | gmane.comp.version-control.subversion.issues |
|---|---|
| Message-ID | <[email protected]> |
[ https://issues.apache.org/jira/browse/SVN-4786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771194#comment-16771194 ]
Julian Foad commented on SVN-4786:
----------------------------------
This WC mods editor is now working well enough for the current shelving test cases.
It is now used for both "shelve" (to write to a shelf storage WC) and "unshelve" (to write to the user's WC). Apart from that, it is only being used so far in the repository-to-WC case of "svn copy", and by "svn x-wc-copy-mods". It isn't yet being used by other modification commands such as svn add/rm/move/propset/patch/merge.
Its notification facility is incomplete: it only sends notifications for "add" and "delete" operations.
> Create a WC working-mods editor
> -------------------------------
>
> Key: SVN-4786
> URL: https://issues.apache.org/jira/browse/SVN-4786
> Project: Subversion
> Issue Type: Task
> Components: libsvn_client
> Reporter: Julian Foad
> Assignee: Julian Foad
> Priority: Major
>
> Create a delta-editor that applies working modifications to the WC.
> It will be useful for implementing things such as shelving, which in principle (and, with this in place, more easily in practice) are just copying a set of modifications from WC to shelf and from shelf to WC.
> Use it to implement the existing client modifications ('svn add', 'svn copy', 'svn rm', etc.). Why? (1) ensure it works for and fully supports those cases; (2) ensure those cases are handled consistently (it will probably reveal inconsistencies in the old implementation).
> See dev@ [thread|http://subversion.apache.org/mail/dev/201811.mbox/<1541760972.3265847.1571178128.7660FB8E%40webmail.messagingengine.com>] "Crazy idea: changes in WC should share an API with changes in repository", from Julian Foad, 2018-11-09.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)