http://bugzilla.moblin.org/show_bug.cgi?id=6448
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #2 from pohly <patrick.ohly(a)intel.com> 2009-11-08 09:14:32 ---
(In reply to comment #1)
This bug has been fixed in the two listed web pages and in
SyncEvolution 0.9.1,
i.e., on the "syncevolution-0-9-x" branch. However, "NEWS" on the
"master"
branch is missing these changes (and the v0.9.1 final release notes). Not sure
what your policy is regarding closing bugs as it relates to branches.
We don't have good support for this in Bugzilla. Typically the status refers to
the branch where the problem was found.
As long
as the changes in "NEWS" from the "syncevolution-0-9-x" branch get
properly
merged into "master", this bug can be considered squashed.
It will get merged eventually. There's no fixed schedule, I just happen to do
it from time to time.
I could change the
status to "RESOLVED" but I don't want to risk interfering with your
workflow.
What's your stance on non-committers changing bug status?
Use common sense ;-) In this case for example, I simply forgot to update the
status and changing the status would have been fine. I would have cleaned this
up during the next bug scrub.
--
Configure bugmail:
http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.