Issue 1786 RND: infrastructure for dealing with new patch types

Title RND: infrastructure for dealing with new patch types
Priority feature Status given-up
Milestone 3.0.0 Resolved in
Superseder patch format should have a version id
View: 1096
Nosy List darcs-devel, dmitry.kurochkin, ganesh, kowey, mndrix
Assigned To

Created on 2010-03-22.13:43:09 by kowey, last changed 2017-07-31.00:35:29 by gh.

msg10414 (view) Author: kowey Date: 2010-03-22.13:43:03
There are a lot of really cool ideas for new patch types:

 - bug-tracking patches
 - hunk moves
 - tree patches (eg. XML)
 - ... and more!

The problem is that whenever you want to define a new patch type, you
have to define how that type commutes with all other patch types.  There
must be some better way.

I don't know how to pin this down to a concrete verifiable next action.
 It seems to just amount to "think really hard" (about what this kind of
infrastructure should achieve and how...)
msg10417 (view) Author: kowey Date: 2010-03-22.16:10:38
It looks like issue1096 may be one of many components of this
infrastructure; however, I want to be careful to point out that for me,
this is more about what goes on in the darcs core than the more mundane
(but still necessary) details about patch formats and what not.
msg10621 (view) Author: kowey Date: 2010-04-02.10:08:29
I've plugged a half-baked idea about dividing patch types into
insta-commuting regions on http://wiki.darcs.net/Ideas/PatchPlugins
Date User Action Args
2010-03-22 13:43:09koweycreate
2010-03-22 16:10:42koweysetnosy: + dagit, ganesh
superseder: + patch format should have a version id
messages: + msg10417
2010-03-22 16:30:11dagitsetnosy: - dagit
2010-03-31 13:16:11koweylinkissue1107 superseder
2010-03-31 13:16:44koweylinkissue311 superseder
2010-04-02 10:08:30koweysetmessages: + msg10621
2010-06-15 21:10:47adminsettopic: - Target-3.0
2010-06-15 21:10:47adminsetmilestone: 3.0.0
2012-02-24 05:47:25mndrixsetnosy: + mndrix
2017-07-31 00:35:29ghsetstatus: needs-reproduction -> given-up