[New: openFATE 318428] Add two new function to glib

Feature added by: Sławomir Lach (Lachu) Feature #318428, revision 1 Title: Add two new function to glib openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: Sławomir Lach (lachu) Partner organization: openSUSE.org Description: Programmers need two new function: is_stack_alloc and is_heap_alloc. It are necessary, because some functions frees memory and it can avoid complications, while is_stack_alloc returns true(in this case memory isn't freed). -- openSUSE Feature: https://features.opensuse.org/318428

Feature changed by: Sławomir Lach (Lachu) Feature #318428, revision 2 Title: Add two new function to glib openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: Sławomir Lach (lachu) Partner organization: openSUSE.org Description: Programmers need two new function: is_stack_alloc and is_heap_alloc. It are necessary, because some functions frees memory and it can avoid complications, while is_stack_alloc returns true(in this case memory - isn't freed). + isn't free). -- openSUSE Feature: https://features.opensuse.org/318428

Feature changed by: Jan Engelhardt (jengelh) Feature #318428, revision 3 Title: Add two new function to glib openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: Sławomir Lach (lachu) Partner organization: openSUSE.org Description: Programmers need two new function: is_stack_alloc and is_heap_alloc. It are necessary, because some functions frees memory and it can avoid complications, while is_stack_alloc returns true(in this case memory isn't free). + Discussion: + #1: Jan Engelhardt (jengelh) (2015-04-30 23:25:01) + This is not the glib feature tracker. Secondly, there is no way to + determine the result for is_stack_alloc, since you can place a thread's + %sp register on some memory block obtained via malloc(). -- openSUSE Feature: https://features.opensuse.org/318428

Feature changed by: akash vishwakarma (vish_99) Feature #318428, revision 4 Title: Add two new function to glib - openSUSE Distribution: Unconfirmed + openSUSE Distribution: Rejected by akash vishwakarma (vish_99) + reject reason: openFATE not meant to request features from upstream. We + might in future but not presently. + OP advised to contact upstream directly. Priority Requester: Neutral Requested by: Sławomir Lach (lachu) Partner organization: openSUSE.org Description: Programmers need two new function: is_stack_alloc and is_heap_alloc. It are necessary, because some functions frees memory and it can avoid complications, while is_stack_alloc returns true(in this case memory isn't free). Discussion: #1: Jan Engelhardt (jengelh) (2015-04-30 23:25:01) This is not the glib feature tracker. Secondly, there is no way to determine the result for is_stack_alloc, since you can place a thread's %sp register on some memory block obtained via malloc(). + #2: akash vishwakarma (vish_99) (2015-05-01 15:31:36) + openFATE is currently is not in shape to request features from + upstream. If you want a feature from glib then contact it's developer. + So, rejecting the feature. For detailed reason openFATE_process + (https://en.opensuse.org/openSUSE:Openfate_process) -- openSUSE Feature: https://features.opensuse.org/318428
participants (1)
-
fate_noreply@suse.de