[p4] Can't add filenames with wildcards [@#%*] in them.
smith_roy at emc.com
Mon Dec 10 11:59:52 PST 2007
Ah. That explains it. I just assumed it would expand "..." with the
normal meaning. This is a really misleading error message. It
should say something like:
Can't add filenames with wildcards [@#%*] or "..." in them.
I'm going to open a support ticket on that.
On Dec 10, 2007, at 2:29 PM, Jeff Campeau wrote:
> The p4 add command only uses command line syntax, so you can't add
> ... since that is a Perforce only wildcard. If you want to add all
> recursively, you need to be a little tricky. Depending on your OS,
> are different ways to do this. Assuming Windows:
> dir /s /b | p4 -x - add
> Make sure you run this from a directory that only includes files you
> actually want to add, running it from C:\ would not be a good idea.
> Also, this may not work well if there are any spaces in the
> directory or
> file names that you are trying to add.
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Roy Smith
> Sent: Monday, December 10, 2007 10:53 AM
> To: Perforce User
> Subject: [p4] Can't add filenames with wildcards [@#%*] in them.
> I'm trying add a new source tree to my depot by doing "p4 add ...",
> but get the message:
> Can't add filenames with wildcards [@#%*] in them.
> As far as I can tell, I don't have any filenames with those
> characters in them. Is there any way to have p4 tell me exactly
> which pathnames it's not happy with?
> Roy Smith <smith_roy at emc.com>
> Software Guy, EMC Common Management Group
> 44 South Broadway, 7th floor
> White Plains, NY 10601
> (914) 580-3427
> AIM: roysmith649
> perforce-user mailing list - perforce-user at perforce.com
Roy Smith <smith_roy at emc.com>
Software Guy, EMC Common Management Group
44 South Broadway, 7th floor
White Plains, NY 10601
More information about the perforce-user