Thread overview
[Issue 9477] String (and array) comparisons are needlessly very slow
Feb 13, 2014
Vladimir Panteleev
Feb 15, 2014
yebblies
Feb 15, 2014
Vladimir Panteleev
Feb 15, 2014
yebblies
Feb 15, 2014
Andrej Mitrovic
February 13, 2014
https://d.puremagic.com/issues/show_bug.cgi?id=9477


Vladimir Panteleev <thecybershadow@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME


-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
February 15, 2014
https://d.puremagic.com/issues/show_bug.cgi?id=9477


yebblies <yebblies@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yebblies@gmail.com
         Resolution|WORKSFORME                  |FIXED


-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
February 15, 2014
https://d.puremagic.com/issues/show_bug.cgi?id=9477



--- Comment #4 from Vladimir Panteleev <thecybershadow@gmail.com> 2014-02-15 17:44:19 EET ---
@Daniel: I thought we need to close bugs that were not fixed in the current development iteration as WORKSFORME? Otherwise they'll end up in this iteration's changelog.

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
February 15, 2014
https://d.puremagic.com/issues/show_bug.cgi?id=9477



--- Comment #5 from yebblies <yebblies@gmail.com> 2014-02-16 02:56:04 EST ---
(In reply to comment #4)
> @Daniel: I thought we need to close bugs that were not fixed in the current development iteration as WORKSFORME? Otherwise they'll end up in this iteration's changelog.

No, WORKSFORME is for bugs with an unknown fix, such as ones that are probably a duplicate of another bug.  This should be in the changelog, and better in the wrong version than not at all.

Basically, keeping the bug tracker correct should be preferred over twisting it to fix the changelog, as this is the real history.

https://d.puremagic.com/issues/page.cgi?id=fields.html#status

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
February 15, 2014
https://d.puremagic.com/issues/show_bug.cgi?id=9477


Andrej Mitrovic <andrej.mitrovich@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andrej.mitrovich@gmail.com


--- Comment #6 from Andrej Mitrovic <andrej.mitrovich@gmail.com> 2014-02-15 07:59:53 PST ---
(In reply to comment #5)
> (In reply to comment #4)
> > @Daniel: I thought we need to close bugs that were not fixed in the current development iteration as WORKSFORME? Otherwise they'll end up in this iteration's changelog.
> 
> No, WORKSFORME is for bugs with an unknown fix, such as ones that are probably a duplicate of another bug.  This should be in the changelog, and better in the wrong version than not at all.

It's not that hard to strip this out of the changelog by hand. It would be good if it was automatic, e.g. if the changelog tool would go through all bugzilla issues and then search whether a commit that fixed the issue (it would have to grep github-bugzilla@puremagic.com's comments) is located in some older tagged branch.

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------