incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse <>
Subject Re: Code Prettifiers
Date Mon, 27 Aug 2012 17:23:45 GMT
Focus on being a contributor and not an arbiter.

If these problems do indeed become problems, then we will deal with them,
however, I don't think we have issues currently, and even if we do, they
are minor IMHO.

+ everything that Michael said, although, I would not shame anyone, and
would simply weigh the value of the contribution with the work required to
appease critical peers, before deciding to pull or push back.

On Mon, Aug 27, 2012 at 10:12 AM, Patrick Mueller <> wrote:

> On Mon, Aug 27, 2012 at 10:33 AM, Andrew Grieve <
> >wrote:
> > ...
> >
> > One thing we may have to do is ask a contributor to enable the git hooks.
> > AFAIK there is no way to enable shared git hooks for a project by
> default,
> > so what we'd have is a directory called "hooks" and you'd need to create
> a
> > symlink for it into your .git/ directory.
> >
> Another option is to do this in some sort of continuous build environment.
>  Where would the "style enforcer" post it's messages though?  Open bugs?
> If no one objects, then I'll pursue this today/tomorrow. My plan is to
> > start with whitespace (sed or awk), get that working, and then see what
> > x-platform open-source formatters exist out there.
> >
> Presumably these hooks need to be portable to *nix and Windows (where mac
> == *nix).  Could we do them in node, without having to shell out to
> command-line tools?  Or maybe have the hooks be js that shell out to
> cmd-line tools you'd need to have installed.
> --
> Patrick Mueller


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message