<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Making p4 and Cygwin play nice</title>
	<atom:link href="http://adamrosenfield.com/blog/2009/11/02/making-p4-and-cygwin-play-nice/feed/" rel="self" type="application/rss+xml" />
	<link>http://adamrosenfield.com/blog/2009/11/02/making-p4-and-cygwin-play-nice/</link>
	<description>Just until I can come up with a better name</description>
	<lastBuildDate>Thu, 08 Dec 2011 02:24:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Ronnie</title>
		<link>http://adamrosenfield.com/blog/2009/11/02/making-p4-and-cygwin-play-nice/comment-page-1/#comment-7994</link>
		<dc:creator>Ronnie</dc:creator>
		<pubDate>Tue, 26 Apr 2011 08:43:06 +0000</pubDate>
		<guid isPermaLink="false">http://adamrosenfield.com/blog/?p=51#comment-7994</guid>
		<description>Nice input. To make P4 work with Cygwin, your program tip was extremely good to do the job for me. Cygwin works pretty well. But one need to check the Main TAR files.</description>
		<content:encoded><![CDATA[<p>Nice input. To make P4 work with Cygwin, your program tip was extremely good to do the job for me. Cygwin works pretty well. But one need to check the Main TAR files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://adamrosenfield.com/blog/2009/11/02/making-p4-and-cygwin-play-nice/comment-page-1/#comment-7965</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Fri, 11 Jun 2010 02:25:13 +0000</pubDate>
		<guid isPermaLink="false">http://adamrosenfield.com/blog/?p=51#comment-7965</guid>
		<description>Thanks for the program and the tip. This was EXACTLY what I have been looking for. I am very very surprised Perforce have not sorted this out in their cygwin command line client.</description>
		<content:encoded><![CDATA[<p>Thanks for the program and the tip. This was EXACTLY what I have been looking for. I am very very surprised Perforce have not sorted this out in their cygwin command line client.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: adam</title>
		<link>http://adamrosenfield.com/blog/2009/11/02/making-p4-and-cygwin-play-nice/comment-page-1/#comment-7948</link>
		<dc:creator>adam</dc:creator>
		<pubDate>Mon, 21 Dec 2009 05:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://adamrosenfield.com/blog/?p=51#comment-7948</guid>
		<description>The Cygwin build of the p4 client (e.g. the one at &lt;&lt;a href=&quot;ftp://ftp.perforce.com/perforce/r09.2/bin.cygwinx86/&quot; rel=&quot;nofollow&quot;&gt;ftp://ftp.perforce.com/perforce/r09.2/bin.cygwinx86/&lt;/a&gt;&gt;) isn&#039;t all that different from the version that comes with P4Win.  It&#039;s more aware of Cygwin features, but to use it, you still need to define your p4 clientspec with a client root of something like &lt;code&gt;/cygdrive/c/blah&lt;/code&gt;.  In particular, if you have a client set up in P4Win with a client root of &lt;code&gt;C:\blah&lt;/code&gt;, the p4 Cygwin build will still be confused.

Use my p4 program (for which I&#039;ve thus far failed to come up with a good name; do you have any suggestions?) to fix this; if you want it to use the Cygwin p4 on the backend instead of the P4Win p4, just replace the executable path in the call to &lt;code&gt;execv()&lt;/code&gt;.</description>
		<content:encoded><![CDATA[<p>The Cygwin build of the p4 client (e.g. the one at &lt;<a href="ftp://ftp.perforce.com/perforce/r09.2/bin.cygwinx86/" rel="nofollow">ftp://ftp.perforce.com/perforce/r09.2/bin.cygwinx86/</a>&gt;) isn&#8217;t all that different from the version that comes with P4Win.  It&#8217;s more aware of Cygwin features, but to use it, you still need to define your p4 clientspec with a client root of something like <code>/cygdrive/c/blah</code>.  In particular, if you have a client set up in P4Win with a client root of <code>C:\blah</code>, the p4 Cygwin build will still be confused.</p>
<p>Use my p4 program (for which I&#8217;ve thus far failed to come up with a good name; do you have any suggestions?) to fix this; if you want it to use the Cygwin p4 on the backend instead of the P4Win p4, just replace the executable path in the call to <code>execv()</code>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Almo</title>
		<link>http://adamrosenfield.com/blog/2009/11/02/making-p4-and-cygwin-play-nice/comment-page-1/#comment-7947</link>
		<dc:creator>Almo</dc:creator>
		<pubDate>Tue, 01 Dec 2009 21:27:14 +0000</pubDate>
		<guid isPermaLink="false">http://adamrosenfield.com/blog/?p=51#comment-7947</guid>
		<description>I tried downloading the cygwin p4, and I get the same error about paths not matching. Sorry to post here about it, but I can&#039;t find info anywhere and I&#039;m getting desperate.</description>
		<content:encoded><![CDATA[<p>I tried downloading the cygwin p4, and I get the same error about paths not matching. Sorry to post here about it, but I can&#8217;t find info anywhere and I&#8217;m getting desperate.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

