[p4] filename case woes: cannot rename Foo.H to Foo.h

[Greg Whitfield]

The problem with the delete/rename/obliterate suggestions is that they
mess with your history. In the case of obliterate, it does something
rather drastic!

An alternative I have used in the past is checkpoint surgery. Edit the
checkpoint to change the filenames in the client specs (I guess the
"Have" tables in the checkpoint), then restore the database.

It was a few years ago when I did this, but I seem to remember that I
only needed to get the users to do a sync to #none, then resync after
the checkpoint has been edited & restored.

Greg
~~~~

 

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Steve M.
Robbins
Sent: 24 July 2007 15:19
To: perforce-user at perforce.com
Subject: [p4] filename case woes: cannot rename Foo.H to Foo.h

Hi,

We have a perforce server running on windows 2003, and mostly
windows-based clients.  Unfortunately, we have a number of check-ins
where "Foo.h" was accidentally named "Foo.H".  This doesn't bother MSVC,
but it does bother gcc on linux.  :-(

How can I rename the file?

I've tried the P4V "Rename/Move" command (gives "no permission" error),
and simply deleting it and re-adding it (file comes back with original
name).

Any ideas?

Thanks,
-Steve
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user