![](https://seccdn.libravatar.org/avatar/25bbc96d9c53647354cb724e744b2222.jpg?s=120&d=mm&r=g)
On Thu, Feb 19, 2009 at 3:46 PM, Tamas Sarga <tamas.sarga2@gmail.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
My question is, what is the desirable method, when I have a clue that a bug fix created another bug. So the fix eventually fixed the issue, but created another one. I reported bnc#398315, what was about repos' changes were saved when I hit abort in the installer. Now it wouldn't be saved even I hit OK and proceed. Should I add another comment to the resolved fixed bug report, or create a new one?
I would re-open it in this case. Being on the receiving end of these reports, it helps to know that the recent work is the first place to look for the source of the bug. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org