<?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: Beginner to Beginner: rsync exclude-from</title>
	<atom:link href="http://www.hyperorg.com/blogger/2008/05/10/beginner-to-beginner-rsync-exclude-from/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hyperorg.com/blogger/2008/05/10/beginner-to-beginner-rsync-exclude-from/</link>
	<description>Let's just see what happens</description>
	<lastBuildDate>Sun, 22 Nov 2009 04:40:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jerk Face McGee</title>
		<link>http://www.hyperorg.com/blogger/2008/05/10/beginner-to-beginner-rsync-exclude-from/comment-page-1/#comment-41002</link>
		<dc:creator>Jerk Face McGee</dc:creator>
		<pubDate>Thu, 05 Feb 2009 20:56:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperorg.com/blogger/?p=6802#comment-41002</guid>
		<description>The manual page does include information about exclude files under &quot;FILTER RULES&quot;. Man pages shouldn&#039;t be read in haste. If you don&#039;t read the ENTIRE man page, you will miss numerous references to some very clearly stated information. 

[snip src=&quot;rsync(1)&quot; ]
       --exclude=PATTERN
              This  option  is  a  simplified form of the --filter option that defaults to an exclude rule and does not allow  the  full  rule-parsing syntax of normal filter rules.See  the  FILTER  RULES section for detailed information on this option.
.....
FILTER RULES
       The filter rules allow for flexible selection of which files to  trans-
       fer  (include)  and  which  files  to skip (exclude).  The rules either
       directly specify include/exclude patterns or  they  specify  a  way  to
       acquire  more include/exclude patterns (e.g. to read them from a file).

       As the list of files/directories to transfer  is  built,  rsync  checks
       each  name  to  be transferred against the list of include/exclude pat-
       terns in turn, and the first matching pattern is acted on:  if it is an
       exclude pattern, then that file is skipped; if it is an include pattern
       then that filename is not skipped; if no  matching  pattern  is  found,
       then the filename is not skipped.

       Rsync  builds  an ordered list of filter rules as specified on the com-
       mand-line.  Filter rules have the following syntax:

              RULE [PATTERN_OR_FILENAME]
              RULE,MODIFIERS [PATTERN_OR_FILENAME]


       You have your choice of using either  short  or  long  RULE  names,  as
       described below.  If you use a short-named rule, the &#039;,&#039; separating the
       RULE from the MODIFIERS is optional.  The PATTERN or FILENAME that fol-
       lows  (when present) must come after either a single space or an under-
       score (_).  Here are the available rule prefixes:

              exclude, - specifies an exclude pattern.
              include, + specifies an include pattern.
              merge, . specifies a merge-file to read for more rules.
              dir-merge, : specifies a per-directory merge-file.
              hide, H specifies a pattern for hiding files from the  transfer.
              show, S files that match the pattern are not hidden.
              protect,  P  specifies a pattern for protecting files from dele-
              tion.
              risk, R files that match the pattern are not protected.
              clear, ! clears the current include/exclude list (takes no arg)


       When rules are being read from a file, empty lines are ignored, as  are
       comment lines that start with a &quot;#&quot;.

       Note that the --include/--exclude command-line options do not allow the
       full range of rule parsing as described above -- they  only  allow  the
       specification of include/exclude patterns plus a &quot;!&quot; token to clear the
       list (and the normal comment parsing when rules are read from a  file).
       If  a  pattern  does  not  begin with &quot;- &quot; (dash, space) or &quot;+ &quot; (plus,
       space), then the rule will be interpreted as if &quot;+ &quot;  (for  an  include
       option) or &quot;- &quot; (for an exclude option) were prefixed to the string.  A
       --filter option, on the other hand, must always contain either a  short
       or long rule name at the start of the rule.

       Note  also that the --filter, --include, and --exclude options take one
       rule/pattern each. To add multiple ones, you can repeat the options  on
       the  command-line, use the merge-file syntax of the --filter option, or
       the --include-from/--exclude-from options.
[/snip]</description>
		<content:encoded><![CDATA[<p>The manual page does include information about exclude files under &#8220;FILTER RULES&#8221;. Man pages shouldn&#8217;t be read in haste. If you don&#8217;t read the ENTIRE man page, you will miss numerous references to some very clearly stated information. </p>
<p>[snip src="rsync(1)" ]<br />
       &#8211;exclude=PATTERN<br />
              This  option  is  a  simplified form of the &#8211;filter option that defaults to an exclude rule and does not allow  the  full  rule-parsing syntax of normal filter rules.See  the  FILTER  RULES section for detailed information on this option.<br />
&#8230;..<br />
FILTER RULES<br />
       The filter rules allow for flexible selection of which files to  trans-<br />
       fer  (include)  and  which  files  to skip (exclude).  The rules either<br />
       directly specify include/exclude patterns or  they  specify  a  way  to<br />
       acquire  more include/exclude patterns (e.g. to read them from a file).</p>
<p>       As the list of files/directories to transfer  is  built,  rsync  checks<br />
       each  name  to  be transferred against the list of include/exclude pat-<br />
       terns in turn, and the first matching pattern is acted on:  if it is an<br />
       exclude pattern, then that file is skipped; if it is an include pattern<br />
       then that filename is not skipped; if no  matching  pattern  is  found,<br />
       then the filename is not skipped.</p>
<p>       Rsync  builds  an ordered list of filter rules as specified on the com-<br />
       mand-line.  Filter rules have the following syntax:</p>
<p>              RULE [PATTERN_OR_FILENAME]<br />
              RULE,MODIFIERS [PATTERN_OR_FILENAME]</p>
<p>       You have your choice of using either  short  or  long  RULE  names,  as<br />
       described below.  If you use a short-named rule, the &#8216;,&#8217; separating the<br />
       RULE from the MODIFIERS is optional.  The PATTERN or FILENAME that fol-<br />
       lows  (when present) must come after either a single space or an under-<br />
       score (_).  Here are the available rule prefixes:</p>
<p>              exclude, &#8211; specifies an exclude pattern.<br />
              include, + specifies an include pattern.<br />
              merge, . specifies a merge-file to read for more rules.<br />
              dir-merge, : specifies a per-directory merge-file.<br />
              hide, H specifies a pattern for hiding files from the  transfer.<br />
              show, S files that match the pattern are not hidden.<br />
              protect,  P  specifies a pattern for protecting files from dele-<br />
              tion.<br />
              risk, R files that match the pattern are not protected.<br />
              clear, ! clears the current include/exclude list (takes no arg)</p>
<p>       When rules are being read from a file, empty lines are ignored, as  are<br />
       comment lines that start with a &#8220;#&#8221;.</p>
<p>       Note that the &#8211;include/&#8211;exclude command-line options do not allow the<br />
       full range of rule parsing as described above &#8212; they  only  allow  the<br />
       specification of include/exclude patterns plus a &#8220;!&#8221; token to clear the<br />
       list (and the normal comment parsing when rules are read from a  file).<br />
       If  a  pattern  does  not  begin with &#8220;- &#8221; (dash, space) or &#8220;+ &#8221; (plus,<br />
       space), then the rule will be interpreted as if &#8220;+ &#8221;  (for  an  include<br />
       option) or &#8220;- &#8221; (for an exclude option) were prefixed to the string.  A<br />
       &#8211;filter option, on the other hand, must always contain either a  short<br />
       or long rule name at the start of the rule.</p>
<p>       Note  also that the &#8211;filter, &#8211;include, and &#8211;exclude options take one<br />
       rule/pattern each. To add multiple ones, you can repeat the options  on<br />
       the  command-line, use the merge-file syntax of the &#8211;filter option, or<br />
       the &#8211;include-from/&#8211;exclude-from options.<br />
[/snip]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: grateful-human</title>
		<link>http://www.hyperorg.com/blogger/2008/05/10/beginner-to-beginner-rsync-exclude-from/comment-page-1/#comment-39994</link>
		<dc:creator>grateful-human</dc:creator>
		<pubDate>Sun, 07 Dec 2008 00:10:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperorg.com/blogger/?p=6802#comment-39994</guid>
		<description>Thanks a lot! I can&#039;t believe that the man page doesn&#039;t include anything on how to format exclude files</description>
		<content:encoded><![CDATA[<p>Thanks a lot! I can&#8217;t believe that the man page doesn&#8217;t include anything on how to format exclude files</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: geekdenz</title>
		<link>http://www.hyperorg.com/blogger/2008/05/10/beginner-to-beginner-rsync-exclude-from/comment-page-1/#comment-39711</link>
		<dc:creator>geekdenz</dc:creator>
		<pubDate>Mon, 24 Nov 2008 02:37:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperorg.com/blogger/?p=6802#comment-39711</guid>
		<description>Agreed, rsync&#039;s exclude-from file is very confusing. I hoped it would do regular expressions but no...

This helped me too. I&#039;m a Software Developer :)

Thanks</description>
		<content:encoded><![CDATA[<p>Agreed, rsync&#8217;s exclude-from file is very confusing. I hoped it would do regular expressions but no&#8230;</p>
<p>This helped me too. I&#8217;m a Software Developer :)</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: soccja</title>
		<link>http://www.hyperorg.com/blogger/2008/05/10/beginner-to-beginner-rsync-exclude-from/comment-page-1/#comment-38546</link>
		<dc:creator>soccja</dc:creator>
		<pubDate>Thu, 02 Oct 2008 05:43:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperorg.com/blogger/?p=6802#comment-38546</guid>
		<description>Joho,
This helped me.
Thanks.</description>
		<content:encoded><![CDATA[<p>Joho,<br />
This helped me.<br />
Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sc</title>
		<link>http://www.hyperorg.com/blogger/2008/05/10/beginner-to-beginner-rsync-exclude-from/comment-page-1/#comment-35668</link>
		<dc:creator>sc</dc:creator>
		<pubDate>Wed, 09 Jul 2008 15:24:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperorg.com/blogger/?p=6802#comment-35668</guid>
		<description>&quot;...&quot;rsync” is where we wash our hands....&quot;

Thanks for that.  It&#039;s the first time rsync has given me something to smile about.

I&#039;m struggling with the &quot;exclude-from&quot; option myself.</description>
		<content:encoded><![CDATA[<p>&#8220;&#8230;&#8221;rsync” is where we wash our hands&#8230;.&#8221;</p>
<p>Thanks for that.  It&#8217;s the first time rsync has given me something to smile about.</p>
<p>I&#8217;m struggling with the &#8220;exclude-from&#8221; option myself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: macchinette video poker</title>
		<link>http://www.hyperorg.com/blogger/2008/05/10/beginner-to-beginner-rsync-exclude-from/comment-page-1/#comment-33485</link>
		<dc:creator>macchinette video poker</dc:creator>
		<pubDate>Thu, 12 Jun 2008 10:12:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperorg.com/blogger/?p=6802#comment-33485</guid>
		<description>&lt;strong&gt;jeux casino en ligne gratuites...&lt;/strong&gt;

A casino online gratis casinos pagina web jugar gratis pagina web poker torneos gratis juego poker erotico...</description>
		<content:encoded><![CDATA[<p><strong>jeux casino en ligne gratuites&#8230;</strong></p>
<p>A casino online gratis casinos pagina web jugar gratis pagina web poker torneos gratis juego poker erotico&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Weinberger (yes, I am related)</title>
		<link>http://www.hyperorg.com/blogger/2008/05/10/beginner-to-beginner-rsync-exclude-from/comment-page-1/#comment-31565</link>
		<dc:creator>Andy Weinberger (yes, I am related)</dc:creator>
		<pubDate>Wed, 14 May 2008 01:44:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperorg.com/blogger/?p=6802#comment-31565</guid>
		<description>And I think &quot;rsync&quot; is where we wash our hands.</description>
		<content:encoded><![CDATA[<p>And I think &#8220;rsync&#8221; is where we wash our hands.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: greg</title>
		<link>http://www.hyperorg.com/blogger/2008/05/10/beginner-to-beginner-rsync-exclude-from/comment-page-1/#comment-31540</link>
		<dc:creator>greg</dc:creator>
		<pubDate>Mon, 12 May 2008 14:07:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperorg.com/blogger/?p=6802#comment-31540</guid>
		<description>oh my god, none of your readers know how to use rsync

including me</description>
		<content:encoded><![CDATA[<p>oh my god, none of your readers know how to use rsync</p>
<p>including me</p>
]]></content:encoded>
	</item>
</channel>
</rss>
