IMHO, this is bloat. The same can be said of files that were updated or patched
(ie display the commit message). There's no reason why anyone couldn't do a
"cvs log file" to find out the message.
Noel
[EMAIL PROTECTED] on 04/24/2000 02:10:49 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: Very minor feature request
Suppose there are two sandboxes in the world: mine, and someone else's.
We both access the same CVS repository.
If The Other Guy removes fileA from his sandbox, then when I do a cvs
update in mine, I get a message that says something like:
warning: fileA is no longer relevant
...and fileA disappears, as it should.
Wouldn't it be nice if the log message given as the reason for removal
were displayed as part of the warning message above? E.g.:
warning: fileA is no longer relevant (Renamed to fileC)
Since removals are most often done to effect a rename operation, that
would help sandbox updaters to figure out why fileA disappeared.
Thoughts?
Cheers,
Laird
