[p4] How do YOU identify the code set for a release?

[Jonathan Biggar]

Stephen Vance wrote:
> Actually, that's not true. The server maintains the "have" list, so as 
> long as the file isn't open for edit the server already knows if it 
> should be identical. If the file has been made writable outside of 
> Perforce's knowledge, then it falls under Perforce's "clobber" rules. 
> If is open for editing (or deleting) then it shouldn't be touched, 
> just like a sync.
>
> Your comment about hard links makes me think that maybe I don't 
> understand exactly what you are trying to do. Are you trying to clone 
> a workspace onto another branch and save disk space through hard links 
> or are you trying to re-home a workspace to a different branch? I was 
> assuming the latter.
>
> If the former, it would be very easy to script a reasonable 
> approximation of this yourself. I know you'd like Perforce to do it 
> for you, but since Perforce doesn't do anything that knows about two 
> workspaces (other than cloning a workspace form), it would surprise me 
> if they would consider this as a request very quickly.
Actually, #3. :)

If a workspace has two branches mapped, it would be nice if the p4 
client used hardlinks to save disk space for files that are identical 
between the two branches.

-- 
Jon Biggar
Floorboard Software
jon at floorboard.com
jon at biggar.org