<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Build and Release Management &#187; Perforce</title>
	<atom:link href="http://allscm.com/archives/category/source-control/perforce/feed" rel="self" type="application/rss+xml" />
	<link>http://allscm.com</link>
	<description>SCM Unleashed!</description>
	<lastBuildDate>Thu, 19 Jan 2012 22:48:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>p4:// &#8220;no permission for operation on files(s)&#8221; Problem?</title>
		<link>http://allscm.com/archives/p4-no-permission-for-operation-on-filess-problem.html</link>
		<comments>http://allscm.com/archives/p4-no-permission-for-operation-on-filess-problem.html#comments</comments>
		<pubDate>Mon, 13 Sep 2010 23:04:33 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Perforce]]></category>
		<category><![CDATA[Source Control]]></category>

		<guid isPermaLink="false">http://allscm.com/?p=328</guid>
		<description><![CDATA[If you ever tried to do an integration activity in Perforce and have gotten a similar error message such as &#8220;no permission for operation on files(s)&#8221; then these are the steps you can do to resolve the problem: Check to make sure your branch spec or the source/target does not have any typo. Check to [...]
No related posts.]]></description>
		<wfw:commentRss>http://allscm.com/archives/p4-no-permission-for-operation-on-filess-problem.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Perforce password (P4PASSWD) invalid or unset error</title>
		<link>http://allscm.com/archives/perforce-password-p4passwd-invalid-or-unset-error.html</link>
		<comments>http://allscm.com/archives/perforce-password-p4passwd-invalid-or-unset-error.html#comments</comments>
		<pubDate>Mon, 28 Jun 2010 19:58:11 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Perforce]]></category>

		<guid isPermaLink="false">http://allscm.com/?p=292</guid>
		<description><![CDATA[If you have gotten &#8220;Perforce password (P4PASSWD) invalid or unset&#8221; error message when you&#8217;ve switched to the ticket based authentication, here&#8217;s what you can do to fix the problem: p4 login -p -a Simple. Straight forward. No related posts.
No related posts.]]></description>
		<wfw:commentRss>http://allscm.com/archives/perforce-password-p4passwd-invalid-or-unset-error.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Importing a new Project in Perforce</title>
		<link>http://allscm.com/archives/perforce-error-in-client-specification-mapping-some_directory-is-not-under-some_depot.html</link>
		<comments>http://allscm.com/archives/perforce-error-in-client-specification-mapping-some_directory-is-not-under-some_depot.html#comments</comments>
		<pubDate>Wed, 20 Jan 2010 20:22:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Perforce]]></category>
		<category><![CDATA[Source Control]]></category>

		<guid isPermaLink="false">http://allscm.com/?p=236</guid>
		<description><![CDATA[I ran into another not-so-clear Perforce error message today while trying to import a new project to an existing depot.  I had a new project1 which I wanted to import into the existing // depot, but when I tried to add via P4V or &#8216;p4 add&#8217; in the command line, I kept getting this message: [...]
No related posts.]]></description>
		<wfw:commentRss>http://allscm.com/archives/perforce-error-in-client-specification-mapping-some_directory-is-not-under-some_depot.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>//projectfoo/bar/&#8230; &#8211; must refer to client &#8216;p4_client&#8217;.</title>
		<link>http://allscm.com/archives/projectfoobar-must-refer-to-client-2.html</link>
		<comments>http://allscm.com/archives/projectfoobar-must-refer-to-client-2.html#comments</comments>
		<pubDate>Fri, 03 Apr 2009 23:01:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Perforce]]></category>
		<category><![CDATA[Source Control]]></category>

		<guid isPermaLink="false">http://allscm.com/?p=118</guid>
		<description><![CDATA[Ever run into this error with Perforce&#8217;s &#8216;p4 changes&#8217; or any other similar command? //projectfoo/bar/&#8230; &#8211; must refer to client &#8216;some_p4_client&#8217;.? I ran into this exact problem today.  I was trying to do a &#8216;p4 changes //projectfoo/bar/&#8230;@xxxxxx,yyyyyy&#8217; to get a history of the changelist and got that error. The symptoms were that doing the same [...]
No related posts.]]></description>
		<wfw:commentRss>http://allscm.com/archives/projectfoobar-must-refer-to-client-2.html/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

