The git error is known and documented, I believe. It is about having git
executable for some parts of the release creation - doesn't affect normal
builds. Perhaps there's a way to mask it with profiles or something..?
On July 18, 2015 1:28:36 AM PDT, Justin Mclean wrote:
>Hi,
>
>+1 binding
>
>I
Please consider using commits@ - that's a well known design pattern
that is used pervasively.
If you need notifications@ in addition, that's okay too, but there are
lots of things that assume commits@
--David
On Fri, Jul 17, 2015 at 1:34 PM, Sean Busbey wrote:
> On Thu, Jul 16, 2015 at 4:50 PM,
