2013/2/27 Jason Hall <[email protected]>: > Having editable issue comments adds a lot of complexity and potentially > harmful side effects. For example, a user could comment "+1 if you like ice > cream!" and receive supportive comments, then edit their comment to say "+1 > if you like the 1981 Chicago Bulls", and now all the supportive comments are > saying something they didn't intend. > > The current behavior also ensures that changes to the issue are reflected in > the comment stream, to preserve the history of the issue > > Perhaps a better solution would be to simply add additional comments to the > issues stating that the revision it points to is now rYYY instead of the > original rXXX. That way it's clear that the change happened, and the issue > reflects both the old and new state. > > - Jason
Thanks for your quick reply Jason. What you suggest would certainly help in case no action whatsoever is taken by Google, but it remains sub optimal as different "rXXX" occurrences can be submitted during the lifetime of an issue. This is a good example: https://code.google.com/p/psutil/issues/detail?id=18#c35 The ideal solution would be to make those "rXXX" occurrences point to the newer Mercurial cset. Is Google planning to do something like that any time soon? Is it even being tracked? If not I guess I'll follow your suggestion but please note that the "SVN to Mercurial/GIT" procedure you're currently offering is suffering a gap which is pretty serious for people like me who have been relying on the "rXXX" notation for many years . -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-code-hosting?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
