To whom it may concern,
I have had this happen a couple of times recently -- I make a change
to something (it has been mostly foundation) and then the next time
I do a "cvs update" it has disappeared.
If you get a "failed up-to-date check", you *must* merge the changes
and not simply overwrite them. In other words, if you are doing:
$ cvs commit whatever
[go through "whatever" failed up-to-date check]
$ cvs update
$ cp my.new.whatever whatever
$ cvs commit whatever
Bad, bad. Please don't do that. If you have a problem with the change
I made, let me know. But don't just overwrite them.
--
Red Hat, Inc., 131 Willow Lane, Floor 2, Oxford, OH 45056
phone +1.513.523.7621 fax 7501 <mheins@redhat.com>
Experience is what allows you to recognize a mistake the second
time you make it. -- unknown
I have had this happen a couple of times recently -- I make a change
to something (it has been mostly foundation) and then the next time
I do a "cvs update" it has disappeared.
If you get a "failed up-to-date check", you *must* merge the changes
and not simply overwrite them. In other words, if you are doing:
$ cvs commit whatever
[go through "whatever" failed up-to-date check]
$ cvs update
$ cp my.new.whatever whatever
$ cvs commit whatever
Bad, bad. Please don't do that. If you have a problem with the change
I made, let me know. But don't just overwrite them.
--
Red Hat, Inc., 131 Willow Lane, Floor 2, Oxford, OH 45056
phone +1.513.523.7621 fax 7501 <mheins@redhat.com>
Experience is what allows you to recognize a mistake the second
time you make it. -- unknown