Jani Tiainen kirjoitti: > Noah Kantrowitz kirjoitti: >> Jani Tiainen wrote: >>> Chris Mulligan kirjoitti: >>>> It seems like ticket comments wouldn't require any sort of diffing, >>>> would they? >>> >>> No if it's pure comment. But along with comment you can change >>> properties of ticket and they might conflict. Problem is that >>> currently ticket update code doesn't handle differences between base, >>> current and new. >>> >>> So what is needed is (might be pretty simple) diff3-like algorithm. >>> Just pickup changes that have happened between base and new, then >>> pickup all differences from base and current. If no conflicts, >>> changes can be pushed with green light, otherwise there must be some >>> intelligent >>> conflict resolution done. >>> >>> Hmm... Sounds something fun that I could take a look at since it's my >>> summer vacation and it's raining all days along. >>> >> >> Is there an echo in here? :-) > > Might be early morning as well and no coffee at home. :) > > But that ticket editing so that there is no conflicts (usually just by > commenting it)is really frustrating. We have hit it few times and it > just feels stupid that when ever you do a plain comment and someone else > does it too, you get that bloodpressure raising message. > > Oh, and I'm going to feel very free to implement it, at least to > tickets. Is there ticket for that? (I'm too lazy to check it)
Replying to myself.. :) Regarding of tickets at least current trunk preserves all changed ticket information, you just get that that conflict message. What comes to comments, It's not straightforward that comments are in cronological line. It can generate duplicate answers if two people comment about same thing, pretty much same way. I like that ajaxian style pull changes while editing style. Then you would be kept pretty much updated, and you can see if someone adds new comments or changes properties... (Which brings problem with visualisation of changes...) -- Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
