fsync(2), fdatasync(2), posix_fadvise(2) and posix_fallocate(2)

[Johan Tibell]

I don't know to be honest.


On Tue, Jun 24, 2014 at 3:12 PM, davean <davean at xkcd.com> wrote:

> Is this documented somewhere? It seems both I and the original submitter
> assumed that tickets would start in the "new" state (and likely be triage
> from there).
>
> -davean
>
>
> On Tue, Jun 24, 2014 at 9:07 AM, Johan Tibell <johan.tibell at gmail.com>
> wrote:
>
>> patch = "Please review"
>>
>> Attachments as in Trac attachments, not links to other websites. This is
>> probably not terribly important, but people tend to not tickets with
>> attachments more.
>>
>>
>> On Tue, Jun 24, 2014 at 2:24 PM, davean <davean at xkcd.com> wrote:
>>
>>> A patch is attached, right there as is a pull location. Not sure what
>>> else you could want.
>>>
>>> Also, the only valid states seem to be (according to trac): closed,
>>> infoneeded, merge, new, patch. I see no "Please review" state. Is how to
>>> use this documented somewhere?
>>>
>>> -davean
>>>
>>>
>>> On Tue, Jun 24, 2014 at 8:15 AM, Johan Tibell <johan.tibell at gmail.com>
>>> wrote:
>>>
>>>> It was in the wrong state. Tickets with attached patches that need to
>>>> be review should be put in the "Please review" state. It might also help to
>>>> actually attach the patch to the ticket.
>>>>
>>>>
>>>> On Tue, Jun 24, 2014 at 1:55 PM, davean <davean at xkcd.com> wrote:
>>>>
>>>>>  I can't find a reason https://ghc.haskell.org/trac/ghc/ticket/8621
>>>>> might have stalled but it seems like it has from my perspective. Can
>>>>> someone tell me I'm wrong or what to do to unstall it?
>>>>>
>>>>> This is very useful functionality that is actually part of IEEE Std
>>>>> 1003.1.
>>>>>
>>>>> -davean
>>>>>
>>>>> _______________________________________________
>>>>> Libraries mailing list
>>>>> Libraries at haskell.org
>>>>> http://www.haskell.org/mailman/listinfo/libraries
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/libraries/attachments/20140624/7ba6e6ba/attachment-0001.html>