patch: strace.1, explication of "unfinished" (repost)

[Tomas Pospisek]

Hello I'm re-posting the below docu patch for consideration.

Would it be possible to include the below documentation improvement in the 
strace manpage?

Is the patch not good enough?

I'd be happy to get some feedback in the form of either:

   - "no we won't include the patch"
   - "please improve this aspect"
   - "committed, thanks"
   - "will commit it later"
   - "have a little patience"

Thanks,
*t

---------- Forwarded message ----------
Date: Thu, 7 Aug 2008 09:47:07 +0200 (CEST)
From: Tomas Pospisek
To: strace-devel
Subject: patch: strace.1, explication of "unfinished"

Hello,

here's a short patch to strace's manpage that documents "unfinished"/"resumed".

I'm not subscribed to the mailing list, thus if there's critique/comments about 
the suggested text then please Cc: me.

THanks,
*t

$ diff -u strace.1.orig strace.1
--- strace.1.orig       2008-08-06 19:45:03.000000000 +0200
+++ strace.1    2008-08-06 20:29:30.000000000 +0200
@@ -147,6 +147,13 @@
  --- SIGINT (Interrupt) ---
  +++ killed by SIGINT +++
  .CE
+If a system call is being executed and meanwhile another one is being called - 
or a signal arrives in the meantime then strace will try to preserve the order 
of those events and mark the ongoing call as being \fIunfinished\fP.
+When the call returns it will be marked as \fIresumed\fP:
+.CW
+[pid 28772] select(4, [3], NULL, NULL, NULL <unfinished ...>
+[pid 28779] clock_gettime(CLOCK_REALTIME, {1130322148, 939977000}) = 0
+[pid 28772] <... select resumed> )      = 1 (in [3])
+.CE
  Arguments are printed in symbolic form with a passion.
  This example shows the shell performing ``>>xyzzy'' output redirection:
  .CW