correctly. Since a list section pushes a sub-object of the
"view" into the "current" context, a partial should recognize
this altered context. The one-line change in mustache.js does
exactly this.

Closes #35.

This reverts commit c2f886602af6ff2d6790b33f87445fc2a5677e0e, reversing
changes made to 88d3d9cf32.

This reverts commit f1f55138a4.

* rbriank/master:
  simple iterator adding \n bug

* jhs/master:
  Output the "Done" message as before
  Actually ignore comment tags; and correct the expected output in the test case
  Refactor template-style builds into a common function
  Execute commands properly. You can see what's happening, and errors halt the build
  Build CommonJS just like any other target, using "pre" and "post" wrappers

* 'master' of github.com:janl/mustache.js:
  allow using sections as context. Patch by dpree.

Conflicts:
	CHANGES.md
	README.md
	mustache.js

If a section key returns a function, it will be called
and passed both the unrendered block of text and a renderer
convenience function.

Given this JS:

  "name": "Tater",
  "bolder": function() {
    return function(text, render) {
      return "<b>" + render(text) + '</b>'
    }
  }

And this template:

  {{#bolder}}Hi {{name}}.{{/bolder}}

We'll get this output:

  <b>Hi Tater.</b>

As you can see, we're pre-processing the text in the block.
This can be used to implement caching, filters (like syntax
highlighting), etc.

You can use `this.name` to access the attribute `name` from
your view.

* defunkt/rake:
  Add descriptions to rake tasks (`rake -T` to see all)
  print => puts

lib/mustache.js is now always kept in sync with mustache.js

(cc @tlrobinson, @boucher)

This reverts commit 738de0bcae.

Conflicts:

	mustache.js