bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Another bug in "admin -m"


From: Paul Edwards
Subject: Re: Another bug in "admin -m"
Date: Sat, 18 Oct 2003 23:53:59 GMT

"Rodolfo Schulz de Lima" <address@hidden> wrote in message news:address@hidden
> Removed one bug that unhide (unhode???) another one :)

Technically, you're looking for "unhid" ("hid" is the proper
tense in this context).  But there's no such word in any tense.
What you want is "exposed".  The opposite of hide is
expose, not unhide.  Someone should clean up English to give
us unhide etc.  The good news is if you can get your friends to
use unhide enough, it becomes "proper English".

"No can do" - courtesy of Hong Kong.

> When you try to commit a file whose only thing that's changed is
> its timestamp, cvs doesn't do anything (even an error message isn't
> displayed),

You don't want an error message when this is done.  Because
if you have 10 files and you've changed 6 of them genuinely,
but the other 4 you made a change, but then changed your mind,
so reversed out the change, then you are left with 4 files that
have changed their timestamp but there is no change.  You don't
want an error on those 4 files.

> and the file remains marked as changed, i.e., CVS/Entries isn't
> updated to the timestamp of the file in repository.

This may be a problem though.  I wonder if it is related to this
one, which bit me?

http://www.google.com.au/groups?selm=vDqVa.21442%24OM3.2246%40news-server.bigpond.net.au&oe=UTF-8&output=gplain

BFN.  Paul.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]