Autogenerated HTML docs for v1.6.6-rc3

1 files changed, 18 insertions, 1 deletions

diff --git a/gitattributes.html b/gitattributes.html
index 2222402ca..540b45003 100644
--- a/gitattributes.html
+++ b/gitattributes.html
@@ -522,6 +522,23 @@ the user to use.  The key phrase here is "more convenient" and not
 intent is that if someone unsets the filter driver definition,

 or does not have the appropriate filter program, the project

 should still be usable.</p></div>

+<div class="para"><p>For example, in .gitattributes, you would assign the <tt>filter</tt>

+attribute for paths.</p></div>

+<div class="listingblock">

+<div class="content">

+<pre><tt>*.c     filter=indent</tt></pre>

+</div></div>

+<div class="para"><p>Then you would define a "filter.indent.clean" and "filter.indent.smudge"

+configuration in your .git/config to specify a pair of commands to

+modify the contents of C programs when the source files are checked

+in ("clean" is run) and checked out (no change is made because the

+command is "cat").</p></div>

+<div class="listingblock">

+<div class="content">

+<pre><tt>[filter "indent"]

+        clean = indent

+        smudge = cat</tt></pre>

+</div></div>

 <h4 id="_interaction_between_checkin_checkout_attributes">Interaction between checkin/checkout attributes</h4>

 <div class="para"><p>In the check-in codepath, the worktree file is first converted

 with <tt>filter</tt> driver (if specified and corresponding driver

@@ -1027,7 +1044,7 @@ frotz   unspecified</tt></pre>
 </div>

 <div id="footer">

 <div id="footer-text">

-Last updated 2009-12-03 09:12:53 UTC

+Last updated 2009-12-17 00:16:03 UTC

 </div>

 </div>

 </body>