On Wed, Apr 29, 2020 at 7:46 PM Adam Thompson <athom...@athompso.net> wrote: > > When I use co(1) with "-l" to check out a file (and/or "ci -l") is there > any way to preserve file ownership and *not* have it reset to the user > running co(1) or ci(1)? > I don't see anything in rcs(1), co(1) or ci(1) that even mentions the > fact that the file will wind up owned by the user running the command. > Ideas? Pointers to documentation?
How could it possibly do anything else unless you always run co as root?