Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 13236] sub_depends entry is added prematurely

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 13236] sub_depends entry is added prematurely
  • Date: 4 Nov 2006 20:33:47 -0000

http://bugs.sourcemage.org/show_bug.cgi?id=13236


acedit AT armory.com changed:

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




------- Additional Comments From acedit AT armory.com 2006-11-04 14:33 -------
When filing a bug report, try to start things off with what the actual major
malfunction is. In this report thats "foo is forced on A", but thats kind of
buried in the report and non-obvious. Instead most of the bug content is on an
entry being prematurely added. Which in so far as the current design is
actually
the proper behavior. This bug is actually a duplicate of 11865 (old
sub-depends
values are used incorrectly).

In anycase, I do appreciate tracing the problem as far as you guys did. But
the
presentation needs some work. I mention this so you can be more effective in
dealing with upstream devs.

If you approach with a claim that some specific part of an internal component
is
broken that comes off as very confrontational, which turns most people off. It
basically boils down to "your code is wrong here" "I don't think so, blah blah
blah" "it did xyz" "and your point is?". If you approach this way your first
impression is that their code is broken, people don't like hearing that, I
know
you don't. After the first statement they kind of stop listening, or at least
become less receptive to whatever else you have to say.

If you start with what the problem is and lead them to what you think the
cause
is, thats a lot less confrontational and they'll be more likely to listen to
you. That basically boils down to "it did xyz" "hmm, thats not good" "i think
its because your code is wrong here" "I think you might have something there".
Here you invoke some sympathy by saying you tried doing something you thought
would work, and then it didn't. Then you help me solve the problem by telling
me
why.

Do you see the difference?

*** This bug has been marked as a duplicate of 11865 ***

--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




Archive powered by MHonArc 2.6.24.

Top of Page