Gerolf Seitz
Gerolf Seitz
I stumbled upon `ekg` on @ocharles' blog and started stripping `ekg` down to `ekg-common` in [my fork](https://github.com/gseitz/ekg-common.git). - I removed all `Snap` related code and introduced `Registry` as a way...
Sure, I'll keep on add things. If nothing else, I get some practice with Haskell ;)
I've been meaning to split the release process into phases, where each phase is a separate setting and can be modified separately. This would make it easier to modify part...
I might change the version handling a bit to provide more flexibility overall. I have something like this in mind: ``` scala case class VersionConfig(validate: String => Boolean, releaseVersion: String...
Hi, so you basically don't want sbt-release to give you a suggestion of the to-be-released version?
FWIW, I can reproduce the exception by supplying a non-existing user/password combination. Sticking ``` haskell closed
Hm, just to be sure, I did a couple of runs with and without the call to `hFlush` and it's now more or less consistently around 3-4 seconds. The other...
In any case, I think it'd be better if a closed connection wouldn't manifest in error at `runGet`.
Changing `SCString::iterator` to `SCString::const_iterator` in the respective lines fixed the compiler errors for me.
What do you think about parsing [giter8-templates](https://github.com/n8han/giter8/wiki/giter8-templates) or some other listing (maybe something along the lines of homebrew) for displaying a list of available templates?