<?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 for #ekynoxe</title>
	<atom:link href="http://blog.ekynoxe.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ekynoxe.com</link>
	<description>development   /   design   /   photography / (and a bit of triathlon)</description>
	<lastBuildDate>Thu, 02 Feb 2012 07:08:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Extending contact form 7 by Matt</title>
		<link>http://blog.ekynoxe.com/2010/09/06/extending-contact-form-7/comment-page-1/#comment-4762</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Thu, 02 Feb 2012 07:08:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ekynoxe.com/?p=210#comment-4762</guid>
		<description>That&#039;s brilliant!! Glad you sorted out.
Al the best!</description>
		<content:encoded><![CDATA[<p>That&#8217;s brilliant!! Glad you sorted out.<br />
Al the best!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending contact form 7 by Miriam de Paula</title>
		<link>http://blog.ekynoxe.com/2010/09/06/extending-contact-form-7/comment-page-1/#comment-4758</link>
		<dc:creator>Miriam de Paula</dc:creator>
		<pubDate>Wed, 01 Feb 2012 22:56:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ekynoxe.com/?p=210#comment-4758</guid>
		<description>Hi Matt.

Very Thank you!

I looked at the plugin&#039;s version, and there was an update (3.1). After upgrading, I got to the extra field work!

Thank you! Thank you!

=)</description>
		<content:encoded><![CDATA[<p>Hi Matt.</p>
<p>Very Thank you!</p>
<p>I looked at the plugin&#8217;s version, and there was an update (3.1). After upgrading, I got to the extra field work!</p>
<p>Thank you! Thank you!</p>
<p>=)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending contact form 7 by Miriam de Paula</title>
		<link>http://blog.ekynoxe.com/2010/09/06/extending-contact-form-7/comment-page-1/#comment-4757</link>
		<dc:creator>Miriam de Paula</dc:creator>
		<pubDate>Wed, 01 Feb 2012 22:48:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ekynoxe.com/?p=210#comment-4757</guid>
		<description>Hi Matt...

Thanks for responding.
I created a  field that lists posts from custom post type. It is working. But I can not send the selected data in the email.

What I did wrong?</description>
		<content:encoded><![CDATA[<p>Hi Matt&#8230;</p>
<p>Thanks for responding.<br />
I created a  field that lists posts from custom post type. It is working. But I can not send the selected data in the email.</p>
<p>What I did wrong?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending contact form 7 by Matt</title>
		<link>http://blog.ekynoxe.com/2010/09/06/extending-contact-form-7/comment-page-1/#comment-4756</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Wed, 01 Feb 2012 22:02:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ekynoxe.com/?p=210#comment-4756</guid>
		<description>Hi Miriam, which version of WPCF7 are you using? It seems there is support for a hidden field now. If you are still using an older version and try to implement the change documented above, have you uninstalled and re-installed the plugin like Dan did? It solved his problem apparently.</description>
		<content:encoded><![CDATA[<p>Hi Miriam, which version of WPCF7 are you using? It seems there is support for a hidden field now. If you are still using an older version and try to implement the change documented above, have you uninstalled and re-installed the plugin like Dan did? It solved his problem apparently.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Extending contact form 7 by Miriam de Paula</title>
		<link>http://blog.ekynoxe.com/2010/09/06/extending-contact-form-7/comment-page-1/#comment-4755</link>
		<dc:creator>Miriam de Paula</dc:creator>
		<pubDate>Wed, 01 Feb 2012 21:47:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ekynoxe.com/?p=210#comment-4755</guid>
		<description>Hi ...

I&#039;m having the same problem as Dan:
http://blog.ekynoxe.com/2010/09/06/extending-contact-form-7/#div-comment-762

Please, somebody help me?
The extra field data are not sent in the mail .... =(</description>
		<content:encoded><![CDATA[<p>Hi &#8230;</p>
<p>I&#8217;m having the same problem as Dan:<br />
<a href="http://blog.ekynoxe.com/2010/09/06/extending-contact-form-7/#div-comment-762" rel="nofollow">http://blog.ekynoxe.com/2010/09/06/extending-contact-form-7/#div-comment-762</a></p>
<p>Please, somebody help me?<br />
The extra field data are not sent in the mail &#8230;. =(</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The 2011 Swashbuckler &#8211; Or how to spend 5h racing by Hyde Park triathlon 2011 &#8211; 2h19&#8217;29&#8243;: Olympic PB! &#124; #ekynoxe</title>
		<link>http://blog.ekynoxe.com/2011/05/31/the-2011-swashbuckler-or-how-to-spend-5h-racing/comment-page-1/#comment-4113</link>
		<dc:creator>Hyde Park triathlon 2011 &#8211; 2h19&#8217;29&#8243;: Olympic PB! &#124; #ekynoxe</dc:creator>
		<pubDate>Thu, 08 Dec 2011 11:43:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ekynoxe.com/?p=539#comment-4113</guid>
		<description>[...] swim was a bit fiesty to start with, but nothing compared to the Swashbuckler earlier this year and I managed to settle in some sort of rhythm without too much problem. The [...]</description>
		<content:encoded><![CDATA[<p>[...] swim was a bit fiesty to start with, but nothing compared to the Swashbuckler earlier this year and I managed to settle in some sort of rhythm without too much problem. The [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Recruiters = Scammers? by Why Linked-in does it wrong &#124; #ekynoxe</title>
		<link>http://blog.ekynoxe.com/2011/08/17/recruiters-scammers/comment-page-1/#comment-4080</link>
		<dc:creator>Why Linked-in does it wrong &#124; #ekynoxe</dc:creator>
		<pubDate>Mon, 05 Dec 2011 22:42:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ekynoxe.com/?p=600#comment-4080</guid>
		<description>[...] while back, I wrote about an experience with a scam/recruiter who managed to call me over at work, trying to [...]</description>
		<content:encoded><![CDATA[<p>[...] while back, I wrote about an experience with a scam/recruiter who managed to call me over at work, trying to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Git post-receive for multiple remote branches and work-trees by Matt</title>
		<link>http://blog.ekynoxe.com/2011/10/22/git-post-receive-for-multiple-remote-branches-and-work-trees/comment-page-1/#comment-4062</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Sun, 04 Dec 2011 18:33:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ekynoxe.com/?p=772#comment-4062</guid>
		<description>Hi Peter, I&#039;ve edited your comments so they look alright. They won&#039;t show indenting as I don&#039;t apply the pretty formatter to those. That&#039;s for another time!

Regarding your code, I can confirm that the second one you posted (for a solution on the same server) does work properly and I&#039;ve updated my original post as well to reflect those changes, which should help a few out there!

Thanks a lot!</description>
		<content:encoded><![CDATA[<p>Hi Peter, I&#8217;ve edited your comments so they look alright. They won&#8217;t show indenting as I don&#8217;t apply the pretty formatter to those. That&#8217;s for another time!</p>
<p>Regarding your code, I can confirm that the second one you posted (for a solution on the same server) does work properly and I&#8217;ve updated my original post as well to reflect those changes, which should help a few out there!</p>
<p>Thanks a lot!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Git post-receive for multiple remote branches and work-trees by Peter</title>
		<link>http://blog.ekynoxe.com/2011/10/22/git-post-receive-for-multiple-remote-branches-and-work-trees/comment-page-1/#comment-4037</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Fri, 02 Dec 2011 18:56:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ekynoxe.com/?p=772#comment-4037</guid>
		<description>And here is a version you can use if your live site is &lt;strong&gt;on another server&lt;/strong&gt;. Keep in mind that you will have to setup a user who can ssh to the other server using keys instead of passwords to authenticate. I’m sure you can find those instructions online.

&lt;code&gt;#!/bin/bash
# {oldrev} {newrev} {refname}
tmpdir=/tmp/git
devpath=/path/to/dev
livepath=/path/to/live
livehost=somehostname
while read oldrev newrev ref
do
        branch=`echo $ref &#124; cut -d/ -f3`
        if [[ &quot;master&quot; == &quot;$branch&quot; ]]; then
                mkdir -p $tmpdir$livepath
                git --work-tree=$tmpdir$livepath checkout -f $branch
                rsync -auv -e ssh --progress --delete $tmpdir$livepath/ $livehost:$livepath
                rm -rf $tmpdir$livepath
                echo &#039;Changes pushed live.&#039;
        elif [[ &quot;development&quot; == &quot;$branch&quot; ]]; then
                git --work-tree=$devpath checkout -f $branch
                echo &#039;Changes pushed to dev.&#039;
        fi
done
&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>And here is a version you can use if your live site is <strong>on another server</strong>. Keep in mind that you will have to setup a user who can ssh to the other server using keys instead of passwords to authenticate. I’m sure you can find those instructions online.</p>
<p><code>#!/bin/bash<br />
# {oldrev} {newrev} {refname}<br />
tmpdir=/tmp/git<br />
devpath=/path/to/dev<br />
livepath=/path/to/live<br />
livehost=somehostname<br />
while read oldrev newrev ref<br />
do<br />
        branch=`echo $ref | cut -d/ -f3`<br />
        if [[ "master" == "$branch" ]]; then<br />
                mkdir -p $tmpdir$livepath<br />
                git --work-tree=$tmpdir$livepath checkout -f $branch<br />
                rsync -auv -e ssh --progress --delete $tmpdir$livepath/ $livehost:$livepath<br />
                rm -rf $tmpdir$livepath<br />
                echo 'Changes pushed live.'<br />
        elif [[ "development" == "$branch" ]]; then<br />
                git --work-tree=$devpath checkout -f $branch<br />
                echo 'Changes pushed to dev.'<br />
        fi<br />
done<br />
</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Git post-receive for multiple remote branches and work-trees by Peter</title>
		<link>http://blog.ekynoxe.com/2011/10/22/git-post-receive-for-multiple-remote-branches-and-work-trees/comment-page-1/#comment-4035</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Fri, 02 Dec 2011 18:38:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ekynoxe.com/?p=772#comment-4035</guid>
		<description>The last one I posted won&#039;t work unless you change the shabang.  Here&#039;s a better version that should be a little easier to read.  I have tested this one successfully.

&lt;code&gt;#!/bin/bash
#   
livepath=&quot;/path/to/your/live&quot;
devpath=&quot;/path/to/your/dev&quot;
while read oldrev newrev ref
do
	branch=`echo $ref &#124; cut -d/ -f3`
	if [[ &quot;master&quot; == &quot;$branch&quot; ]]; then
		git --work-tree=$livepath checkout -f $branch
		echo &#039;Changes pushed live.&#039;
	elif [[ &quot;development&quot; == &quot;$branch&quot; ]]; then
		git --work-tree=$devpath checkout -f $branch
		echo &#039;Changes pushed to dev.&#039;
	fi
done&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>The last one I posted won&#8217;t work unless you change the shabang.  Here&#8217;s a better version that should be a little easier to read.  I have tested this one successfully.</p>
<p><code>#!/bin/bash<br />
#<br />
livepath="/path/to/your/live"<br />
devpath="/path/to/your/dev"<br />
while read oldrev newrev ref<br />
do<br />
	branch=`echo $ref | cut -d/ -f3`<br />
	if [[ "master" == "$branch" ]]; then<br />
		git --work-tree=$livepath checkout -f $branch<br />
		echo 'Changes pushed live.'<br />
	elif [[ "development" == "$branch" ]]; then<br />
		git --work-tree=$devpath checkout -f $branch<br />
		echo 'Changes pushed to dev.'<br />
	fi<br />
done</code></p>
]]></content:encoded>
	</item>
</channel>
</rss>

