On Tue, Oct 1, 2013 at 8:10 AM, Liebig, Holger
<holger.lie...@ts.fujitsu.com> wrote:
>>
>> Holger,
>>
>> despite this is a good news, I wonder whether it's really necessary to have
>> three tickets to track one feature.
>>
>> * https://sourceforge.net/p/ipmitool/feature-requests/32/ - created on
>> 2013-04-02 by myself
>> * https://sourceforge.net/p/ipmitool/patches/81/ - created on 2013-09-02 by
>> you
>> * https://sourceforge.net/p/ipmitool/patches/83/ - created on 2013-09-30 by
>> you
>>
>> I find this state a bit confusing. I understand it's probably impossible to
>> attach file to somebody's else ticket(I haven't tested new SF.net yet).
>> What I don't understand is why you have created a new ticket. Moreover, why
>> haven't you updated your original ticket instead of creating a new one.
>>
> [Liebig, Holger]
> Unfortunately, I cannot edit/delete/change the status of my own tickets

Despite what you're saying is true, do you really feel like you have
to edit status of the ticket? I believe to remove previous version of
patch or simply posting new message to ticket in question with words:
``Here is updated version, ignore the original'' would be more than
sufficient. Other people did and do it this way.

> I also think it is a good idea to distinguish between feature requests and 
> actual patches (I had left a notice on your ticket referring to my first 
> version of the patch).

Uh, in which way exactly? What do you mean? I hope you don't mean to
tell me feature request ticket and patch ticket are two different
things, are you? As a matter of fact, "patches" queue should be used
scarcely, if it should be used at all. In other words, we could either
remove it completely(somewhat planned) or rename it to "trash",
"dosnt-fit-anywhere-else" etc., because that's the perception of this
ticket queue. I, I can't speak for others, fail to see purpose of this
queue. But anyone feel free to explain it to me.

Best regards,
Z.

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
Ipmitool-devel mailing list
Ipmitool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel

Reply via email to