The point being that it wouldn't be the file you would edit. And many +-1's to Noah's scheme to hand out more commit bits. Bring it.
Sent from the ocean floor On 3 Nov 2012, at 16:44, Octavian Damiean <mainer...@gmail.com> wrote: > Compiled artifact in this case means, compiled LESS files to CSS (minified > or not), JavaScript (minified or not) and HTML. So no bytecode, it would > still be readable (except minified JS and CSS are a bit hard to read bit > still plaintext). > > Cheers, > Octavian > > On Sat, Nov 3, 2012 at 5:37 PM, Noah Slater <nsla...@apache.org> wrote: >> >> Also, Bob sed: >> >> If the choice is node as a build dependency versus checking in compiled >>> artifacts, I choose node. >> >> >> Perhaps someone can clarify for me what a compiled artefact is? We can't >> ship compiled code. We can ship compressed or package code. But if we're >> compiling code into bytecode or machine code, that is a complete no-no in >> both our repos and our releases. >> >> -- >> NS >>
