new: lining.js

Third time is the charm?
My counter argument to that is we are less likely to react to new files
being published. On the flip side once we know they're there we can make
config changes
On Nov 20, 2014 6:04 PM, "Tom Byrer" <notifications@github.com> wrote:

> In files/lining.js/update.json:
>
> > @@ -0,0 +1,9 @@
> > +{
> > +  "packageManager": "github",
> > +  "name": "lining.js",
> > +  "repo": "zmmbreeze/lining.js",
> > +  "files": {
> > +    "basePath": "build/",
> > +    "include": ["lining.min.js", "lining.effect.min.js"]
>
> I'd personally rather leave it in please. I'd prefer to manually whitelist
> additions than have to back out of experiments
> <https://github.com/zmmbreeze/lining.js/issues/3#issuecomment-63590875>.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/jsdelivr/jsdelivr/pull/2445/files#r20685099>.
>