[p4] Bug in "p4 dirs"? Doesn't list unless sync'd
Robert Cowham
robert at vaccaperna.co.uk
Tue Mar 21 07:44:03 PST 2006
Don't forget that your shell may expand * unless you quote the argument ...
$ p4 dirs -D "//vega/xp/dev/rickm/SCM/sam/zsignal/*"
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Rick
> Macdonald
> Sent: 21 March 2006 15:20
> To: Perforce Users
> Subject: Re: [p4] Bug in "p4 dirs"? Doesn't list unless sync'd
>
> Good point. So, I checked tkp4, which I wrote, and it does
> list all the directories. The difference is that tkp4 uses
> %%1 as a wildcard whereas the script that I'm writing uses
> "*". It's been so long, I don't remember how I decided to use
> %%1 (which used to be just %1) instead of *.
>
> p4v shows "*" in the log pane but surely it's using the API
> and not really running p4, so we don't really know what it's
> using for a wildcard.
>
> Note how "v5.00" doesn't show up when I use the "*", until I
> sync at least one file. Still seems like a bug to me.
>
> $ p4 dirs -D //vega/xp/dev/rickm/SCM/sam/zsignal/%%1
> //vega/xp/dev/rickm/SCM/sam/zsignal/v4.00
> //vega/xp/dev/rickm/SCM/sam/zsignal/v4
> //vega/xp/dev/rickm/SCM/sam/zsignal/v5.00
> //vega/xp/dev/rickm/SCM/sam/zsignal/v5
> //vega/xp/dev/rickm/SCM/sam/zsignal/xp
> $ p4 dirs -D //vega/xp/dev/rickm/SCM/sam/zsignal/*
> //vega/xp/dev/rickm/SCM/sam/zsignal/v4
> //vega/xp/dev/rickm/SCM/sam/zsignal/v4.00
> //vega/xp/dev/rickm/SCM/sam/zsignal/v5
> //vega/xp/dev/rickm/SCM/sam/zsignal/xp
> $ p4 sync //vega/xp/dev/rickm/SCM/sam/zsignal/v5.00/README
> //vega/xp/dev/rickm/SCM/sam/zsignal/v5.00/README#1 - added as
> /vega/xp/dev/rickm/SCM/sam/zsignal/v5.00/README
> $ p4 dirs -D //vega/xp/dev/rickm/SCM/sam/zsignal/*
> //vega/xp/dev/rickm/SCM/sam/zsignal/v4
> //vega/xp/dev/rickm/SCM/sam/zsignal/v4.00
> //vega/xp/dev/rickm/SCM/sam/zsignal/v5
> //vega/xp/dev/rickm/SCM/sam/zsignal/v5.00
> //vega/xp/dev/rickm/SCM/sam/zsignal/xp
> $ p4 sync //vega/xp/dev/rickm/SCM/sam/zsignal/v5.00/README#none
> //vega/xp/dev/rickm/SCM/sam/zsignal/v5.00/README#1 - deleted
> as /vega/xp/dev/rickm/SCM/sam/zsignal/v5.00/README
> $ p4 dirs -D //vega/xp/dev/rickm/SCM/sam/zsignal/*
> //vega/xp/dev/rickm/SCM/sam/zsignal/v4
> //vega/xp/dev/rickm/SCM/sam/zsignal/v4.00
> //vega/xp/dev/rickm/SCM/sam/zsignal/v5
> //vega/xp/dev/rickm/SCM/sam/zsignal/xp
>
>
> Robert Cowham wrote:
>
> >Are you sure - sounds surprising to me - if it didn't work then you
> >could never browse stuff in the GUI.
> >
> >
> >
> >>-----Original Message-----
> >>From: perforce-user-bounces at perforce.com
> >>[mailto:perforce-user-bounces at perforce.com] On Behalf Of Rick
> >>Macdonald
> >>Sent: 21 March 2006 01:27
> >>To: Perforce Users
> >>Subject: [p4] Bug in "p4 dirs"? Doesn't list unless sync'd
> >>
> >>I just discovered that p4 dirs does not list directories
> that are not
> >>sync'd to at least one client, somewhere.
> >>
> >>Is this a known issue? Seems like a bug to me.
> >>
> >>I'm writing a script that needs to reliably determine what
> dirs exist
> >>in a certain area of the depot. There is a time window where files
> >>might not be sync'd anywhere yet.
> >>
> >>Is there some other efficient way to get dirs? All I can
> think of is
> >>"p4 files".
> >>
> >>...RickM...
> >>
> >>
> >
> >
> >
> >
> >
>
> _______________________________________________
> perforce-user mailing list - perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>
More information about the perforce-user
mailing list