[p4] Re: Branching they easy way?

[Scott Blachowicz]

Dave Birkhead <daveb at extensity.com> wrote:

> I agree with you, but there is a work around.
> what I do is map all relevant codelines in to a client.
> Then a alias(using subst on NT or soft links in Unix) for my 
> development work area.

It would be nice, however, if the p4 commands were able to resolve the
"aliased" location back to its actual location.  For example, (on NT)
if I do this:

	SUBST P: H:\Projects\Branch1

then have H:\Projects in my p4 client viewspec.  I can do sync's and
stuff fine, but if I do this:

	P:
    cd subdir1
	p4 edit *.cpp

the p4 command doesn't know that P:\subdir1 is the same as
H:\Projects\Branch1 so you get the

    Path 'P:\subdir1\*.cpp' is not in under client's root 'H:\Projects'.

type of error.  I believe you would get the same sort of error on Unix
if you use a shell that tracks & sets the PWD environment variable
"for you".  Something like this, I think...

    cd /homes/scott
	ln -s /homes/scott/Projects/Branch1 Dev
	cd Dev

At this point, the PWD envar would be set to "/homes/scott/Dev" and
based on other things I've seen, that would get used by the p4
commands.  And I just tested that out...does the same sort of thing.
It might be nice if the 'p4' command would check the "real" directory
to see if it's in the client's root after the $PWD lookup fails.  Or,
similarly, with NT subst'd drives (check the local drive that the
subst refers to).

Scott.Blachowicz at seaslug.org