After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 334086 - SVN-CVS Compatibility
SVN-CVS Compatibility
Status: RESOLVED DUPLICATE of bug 318480
Product: planner
Classification: Other
Component: General
0.13
Other All
: Normal enhancement
: ---
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2006-03-10 01:53 UTC by John
Modified: 2008-12-04 15:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description John 2006-03-10 01:53:41 UTC 
I'm using CVS/SVN to store my planner file. Since SVN is renumbering tasks,
concurrent editing always leads to conflict.

I suggest to use symbolic IDs that are, e.g., derived as a hash with some salt
from the name. This means that unlike a task itself changes, the file wont change.

As a consequence, task/resource/... changes are localized and can be merged into
a file using the normal CVS/SVN merging functions.
Comment 1 John 2006-03-10 02:08:21 UTC 
To "reproduce":
- Create a number of tasks and store the file (or use any existing project) as 
  file1.planner
- Insert a new task at the beginning of the task list
- Store as file2.planner
- Do a diff between file1.planner and file2.planner

What you'll see is that the complete XML has changed even though adding a single line should have sufficed.

Comment: For representing visual order, a linked list should be the right approach: After entering a new task on position 1, the task on position 2 will need to be assigned a new list predecessor.
Comment 2 Gilles Dartiguelongue 2008-12-04 15:45:03 UTC 
actually this is a duplicate of bug #318480

*** This bug has been marked as a duplicate of 318480 ***