From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: "wilson@ds.net" <wilson@ds.net>, "'D. Boland'" <daniel@boland.nl>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: vi stealing SYSTEM-owned permissions and ownership
Date: Mon, 04 Nov 2013 14:54:00 -0000 [thread overview]
Message-ID: <5F8AAC04F9616747BC4CC0E803D5907D0C40C672@MLBXv04.nih.gov> (raw)
In-Reply-To: <EF57884064F9460EBA1AA99C06CE8A67@NCC1701>
> > Haha, yes. But if my students have to administer remote
> production-machines, most of the time they have no other option. I want them
> to succeed where others fail.
Reading this thread, it looks like it digressed far away from the original point
($subject) as to why "vi" did not keep the original owner of an edited file.
(also pointed out was that "nano" did)... A reasonable expectation, IMO.
Anton Lavrentiev
Contractor NIH/NLM/NCBI
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2013-11-04 14:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 12:55 D. Boland
2013-11-02 13:36 ` Brian S. Wilson
2013-11-02 18:42 ` Andrey Repin
2013-11-02 21:58 ` D. Boland
2013-11-02 22:35 ` Andrey Repin
2013-11-03 18:47 ` D. Boland
2013-11-03 22:05 ` Andrey Repin
2013-11-04 11:23 ` Brian S. Wilson
2013-11-04 14:54 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] [this message]
2013-11-04 17:05 ` Larry Hall (Cygwin)
2013-11-05 5:54 ` D. Boland
2013-11-05 17:38 ` Achim Gratz
2013-11-08 14:25 ` D. Boland
2013-11-08 15:59 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2013-11-08 20:20 ` Andrey Repin
2013-11-27 18:11 ` D. Boland
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=5F8AAC04F9616747BC4CC0E803D5907D0C40C672@MLBXv04.nih.gov \
--to=lavr@ncbi.nlm.nih.gov \
--cc=cygwin@cygwin.com \
--cc=daniel@boland.nl \
--cc=wilson@ds.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 read-only IMAP folder(s) and NNTP newsgroup(s).