From: Scott Schwartz schwartz@galapagos.cse.psu.edu
Subject: ape rename bug
Date: Thu, 5 Sep 1996 03:09:37 -0400 [thread overview]
Message-ID: <19960905070937.Wsn3FzZyguZyNZ5b4bJ-GUF7FHtZdqUg3YxRG9KRdDE@z> (raw)
In APE, if rename has to copy, it never deletes the source file.
In that case, something like the following is needed:
if (n == 0) {
if(_REMOVE(from) < 0){
_syserrno();
return -1;
}
}
reply other threads:[~1996-09-05 7:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19960905070937.Wsn3FzZyguZyNZ5b4bJ-GUF7FHtZdqUg3YxRG9KRdDE@z \
--to=9fans@9fans.net \
/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).