linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David Prévot" <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	"David Prévot" <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Subject: [PATCH] fexecve.3: ffix
Date: Tue, 29 Oct 2013 22:37:32 -0400	[thread overview]
Message-ID: <1383100652-7236-1-git-send-email-taffit@debian.org> (raw)

---
 man3/fexecve.3 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man3/fexecve.3 b/man3/fexecve.3
index f228f00..03a00da 100644
--- a/man3/fexecve.3
+++ b/man3/fexecve.3
@@ -114,7 +114,7 @@ Simply opening the file, checksumming the contents, and then doing an
 would not suffice, since, between the two steps, the filename,
 or a directory prefix of the pathname, could have been exchanged
 (by, for example, modifying the target of a symbolic link).
-.BR fexecve()
+.BR fexecve ()
 does not mitigate the problem that the
 .I contents
 of a file could be changed between the checksumming and the call to
-- 
1.8.4.rc3

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2013-10-30  2:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30  2:37 David Prévot [this message]
     [not found] ` <1383100652-7236-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-11-07 16:55   ` [PATCH] fexecve.3: ffix Michael Kerrisk (man-pages)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1383100652-7236-1-git-send-email-taffit@debian.org \
    --to=taffit-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).