Log message:
devel/garden: update to 0.8.0

v0.8.0
Features:
 - garden now supports a grafts feature that allows you to stitch configuration
   entities from separate garden files into a graft-specific namespace.
   Trees and variables from grafted configurations can be referenced using
   graft:: namespace qualifiers.
 - garden grow can now configure upstream branches.
 - garden grow can now configure gitconfig settings with multiple values using
   git config --add <name> <value>.

v0.7.0
Features:
 - Trees, Groups, Gardens and Commands defined in the top-level garden.yaml
   can now override entries defined via garden.includes. Configuration entities
   now follow "last one wins" semantics -- if the same entity is defined in
   multiple includes files then only the final definition will be used. (#14)
   (#15)
 - Trees now sparsely override existing entries. This behavior allows a tree
   definition to replace just the url field, or to replace individual tree
   commands while retaining the rest. Use replace: true in a Tree definition in
   order to completely replace the existing entry instead of sparsely
   overridding it.
 - Improved shell completions for garden, garden init and garden plant.

Packaging
 - 0323pin packaged garden for pkgsrc/NetBSD and merged the package into the
   main branch! (#13)

Log message:
garden: import package

Garden streamlines development workflows that involve a loosely-coupled set
of multiple, independent Git trees.

Garden allows you to define dynamic relationships and workflows between these
repositories using a declarative YAML config file that can be shared and used
as a bootstrapping mechanism for getting a auditable, from-source project
cloned, built, installed and running with minimal effort for consumers
of a Garden file.

Garden sits above any individual project's build scripts and conventions.
Garden is all about making it easy to remix and reuse libraries maintained in
seperate Git repositories.