Fixed 'separator' typos
Merge remote-tracking branch 'tchaudhri/tchaudhri_join_func_doc_typo'

* tchaudhri/tchaudhri_join_func_doc_typo:
  Fixed 'separator' typos

Closes GH-196
(Main) fix typo in pick error message

Update pick error message "at least one non empty value"
Merge branch 'fix-pick-error-typo'

* fix-pick-error-typo:
  (Main) fix typo in pick error message

Closes GH-197
(#20200) Add a recursive merge function.

Issue #20200 notes that the merge function does not
support nested hashes.

To prevent unintended side effects with changing merge,
add a deep_merge function instead.
Merge branch 'fix/master/add_recursive_merge'

* fix/master/add_recursive_merge:
  (#20200) Add a recursive merge function.

Closes GH-189

This patch changes the original pull request to draw in the overlay function as
a Proc and make use of Hash.merge {} for resolving key conflicts.
Fix the tests on osx
calling rspec directly makes this not pass ruby -c. adjusting to be in line with the rest.
Remove unintentional link from README

Markdown interprets [] folowed by () as a link, which was a 404 and not
the intention of the original author. This patch ensures that the
document reads as intended, without the link.
Add rake tasks to validate and lint files and check with Travis

This patch adds the ability to validate syntax of manifests, templates,
and ruby files in lib/ via `rake validate` and the linting of manifests
with puppet-lint via `rake lint`. These two commands are chained with
running the spec tests in Travis to ensure there are no syntax or style
issues.
Pin rspec-puppet to 0.1.6 for now as the change to 1.0.0 has broken
things involving Mocha badly.
Merge pull request #210 from apenney/temp-fix

Pin rspec-puppet to 0.1.6 for now as the change to 1.0.0 has broken
(#23381) add is_bool() function
Merge pull request #200 from bobtfish/fix_tests_on_osx

Fix the tests on osx
(maint) Update README stating stdlib 4.x supports Puppet 2.7.x

Without this patch there is a disconnect between the documentation in
the README and our decision to not merge pull requests into the 4.x
series that break compatibility with Puppet 2.7.x

For example:

    @jeffmccune I think the real issue here is that "policy" is out of sync with
    the documentation. The README claims that 4.x does not support puppet 2.7.x,
    yet the "policy" is not to merge patches that break 2.7.x. Due to that I'm sure
    there are a lot of 2.7.x installations out there that have a 4.x version of
    stdlib installed. That's going to cause a rather rude surprise if some future
    version of 4.x stops working where a prior minor release was functioning.

    I'd like to suggest that the documentation be changed to reflect 4.x supporting
    2.7.x and that a new major version bump is made when 2.7.x support can in fact
    be dropped. An alternative solution would be update the README with a note to
    developers about the kinda/sorta/maybe/fishy/quasi support of 2.7.x.

Please also see this discussion:
https://github.com/puppetlabs/puppetlabs-stdlib/pull/176#issuecomment-30251414
Merge pull request #203 from dreamlibrarian/fix/is_function_available-ruby_c

calling rspec directly makes is_function_available.rb not pass ruby -c
Merge pull request #207 from ghoneycutt/remove_unintentional_link

Remove unintentional link from README
Merge pull request #208 from ghoneycutt/add_validation

Add rake tasks to validate and lint files and check with Travis
Merge pull request #211 from jhoblitt/function_is_bool

(#23381) add is_bool() function
(Maint) Update stubbing to work with facter 1.7.4

Facter 1.7.4 changed how it decides on what directory to look in for
facts.d based on the user it is running as. This stubs out that bit of
code to make it think it is running as root.