merqumab

If you have multiple Slacks, it's not. You can cycle through all your connected Slacks with the app.

See this 2012 thread https://github.com/torvalds/linux/pull/17#issuecomment-56546...

I'm a bit disappointed there are no tests. I've always wondered how Google handles testing on internal Android projects (especially since it's a bit of a sore spot for Android [1]). It would've been great to see a "real world", official example.

[1] https://github.com/JakeWharton/gradle-android-test-plugin#de...

I really like how Gradle has solved this problem. You check in the Gradle wrapper (http://www.gradle.org/docs/current/userguide/gradle_wrapper....) into your source control (it's only 56K), and it automatically fetches Gradle for you if you don't have it. Updating the project's Gradle version is just a matter of changing one or two lines.

It's cool to think that the only requirement for anybody to jump into a Gradle project is to have the JDK installed. "git clone <project>", "./gradlew assemble" is all it takes for you to fetch all your dependencies and build the project.

I think it'd be interesting to see if Vagrant could incorporate something like this; it sounds like it would help your use case.

You could always set the script to only run the tests on certain branches on pre-commit. (i.e. if branch name is not master, exit 0)

If you haven't already, it might be a good idea to vote for that feature: http://youtrack.jetbrains.com/issue/VIM-448 and http://youtrack.jetbrains.com/issue/VIM-518

Which would you recommend to read first?

Unsubscribe from the default subreddits and you'll find more intelligent discourse.

I think having Google retail stores would've been great and given them some exposure and credibility with people less familiar with phones. That said, I would have also found it unusual given their push to sell things in the Play Store and the fact that they don't have that much hardware to sell.