[m-rev.] diff: fix mercury_wrapper.c snprintf bug

[Mark Brown]

On 17-Sep-2008, Julien Fischer <juliensf at csse.unimelb.edu.au> wrote:
>
> On Wed, 17 Sep 2008, Peter Ross wrote:
>
>> On Wed, Sep 17, 2008 at 9:10 AM, Julien Fischer
>> <juliensf at csse.unimelb.edu.au> wrote:
>>>
>>> On Wed, 17 Sep 2008, Peter Ross wrote:
>>>
>>>> On Wed, Sep 17, 2008 at 4:39 AM, Julien Fischer
>>>> <juliensf at csse.unimelb.edu.au> wrote:
>>>>>
>>>>> On Tue, 16 Sep 2008, Peter Ross wrote:
>>>>>
>>>>>> runtime/mercury_wrapper.c:
>>>>>>       Use _snprintf if snprintf not defined.
>>>>>
>>>>> You should close bug #72.
>>>>>
>>>> I've marked it resolved.  I can also mark it closed, but first wanted
>>>> to query who should close bugs?
>>>
>>> Marking it as resolved will be sufficient.
>>>
>> My question still stands, who is responsible for closing a bug?
>
> We don't currently use the closed status in any way that is meaningfuly
> distinct from resolved, so no-one.

I suppose you can close a bug without resolving it (by deciding that it
will never be fixed, for example), but that would be a group decision
rather than one person's responsibility.  Mostly we just consider "resolved"
to be the final state of a bug, and leave it at that.

Cheers,
Mark.

--------------------------------------------------------------------------
mercury-reviews mailing list
Post messages to:       mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au
--------------------------------------------------------------------------