From: Helge Kreutzmann <debian@helgefjell.de>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: Errors in man pages, here: rename(2): Content
Date: Sun, 26 Apr 2020 13:12:52 +0200 [thread overview]
Message-ID: <20200426111252.GE2031@Debian-50-lenny-64-minimal> (raw)
In-Reply-To: <4a026c82-7dc1-164b-186d-b4dceb3ebea9@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
Hallo Michael,
On Mon, Apr 20, 2020 at 11:40:26AM +0200, Michael Kerrisk (man-pages) wrote:
> On 4/19/20 8:48 AM, Helge Kreutzmann wrote:
> > **
> >
> > If newpath exists, this is already the reason for the failure?
> >
> > "If I<newpath> exists but the operation fails for some reason, B<rename>() "
> > "guarantees to leave an instance of I<newpath> in place."
>
> I do not understand this report. Please elaborate.
Trying to 2nd guess what the original translator, who unfortunately is
no longer active, might have thought:
If you want to rename but the new path already exists, how can there
be other reasons for failure at all?
If this still does not make sense, please close this report without
changes, of course.
Greetings
Helge
--
Dr. Helge Kreutzmann debian@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-26 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 6:48 Errors in man pages, here: rename(2): Content Helge Kreutzmann
2020-04-20 9:40 ` Michael Kerrisk (man-pages)
2020-04-26 11:12 ` Helge Kreutzmann [this message]
2020-04-26 14:24 ` Michael Kerrisk (man-pages)
2020-04-26 16:17 ` Helge Kreutzmann
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=20200426111252.GE2031@Debian-50-lenny-64-minimal \
--to=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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).