| If you want to clone an svn repository with git-svn but don't want it to push all the existing branches, here's what you should do. | |
| * Clone with git-svn using the -T parameter to define your trunk path inside the svnrepo, at the same time instructing it to clone only the trunk: | |
| git svn clone -T trunk http://example.com/PROJECT | |
| * If instead of cloning trunk you just want to clone a certain branch, do the same thing but change the path given to -T: | |
| git svn clone -T branches/somefeature http://example.com/PROJECT |
| #!/usr/bin/perl | |
| use File::Find; | |
| my $backup_root = "/path/to/folder" | |
| # purge backups older than AGE in days | |
| my @file_list; | |
| my @find_dirs = ($backup_root); # directories to search | |
| my $now = time(); # get current time | |
| my $days = 30; # how many days old |
| #!/bin/sh | |
| exec /Users/sroebuck/local/bin/scalas $0 $@ | |
| !# | |
| /*** | |
| libraryDependencies ++= Seq( | |
| "com.github.scala-incubator.io" %% "scala-io-file" % "0.2.0", | |
| "joda-time" % "joda-time" % "2.0", | |
| "org.joda" % "joda-convert" % "1.1" | |
| ) | |
| */ |
| [emacs] | |
| name=Emacs 24.2 repo | |
| baseurl=http://pj.freefaculty.org/EL/6/x86_64/ | |
| failovermethod=priority | |
| enabled=1 | |
| gpgcheck=1 | |
| gpgkey=http://pj.freefaculty.org/EL/PaulJohnson-BinaryPackageSigningKey |
| import scala.language.experimental.macros | |
| import scala.reflect.macros.blackbox.Context | |
| import play.api.libs.json.{Format, Writes, Reads, OWrites} | |
| object PlayJson{ | |
| def reads[A <: AnyRef]: Reads[A] = macro readsImpl[A] | |
| def readsImpl[A <: AnyRef : c.WeakTypeTag](c: Context): c.Expr[Reads[A]] = { | |
| import c.universe._ |
| /** | |
| * K.jpg's OpenSimplex 2, smooth variant ("SuperSimplex") | |
| * | |
| * More language ports, as well as legacy 2014 OpenSimplex, can be found here: | |
| * https://github.com/KdotJPG/OpenSimplex2 | |
| */ | |
| public class OpenSimplex2S { | |
| private static final long PRIME_X = 0x5205402B9270C86FL; |
NOTE: a more up-to-date version of this can be found on my blog
A few days ago, version 1.9 of the Nix package manager was released. From the release notes:
nix-shell can now be used as a #!-interpreter. This allows you to write scripts that dynamically fetch their own dependencies.
Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.
Translations: (No guarantee that the translations are up-to-date)
Want to use Nix for development but you're not sure how? Concerned about the
fluidity of nixpkgs channels or not being able to easily install arbitrary
package versions?
When I first heard about Nix it seemed like the perfect tool for a developer. When I tried to actually use it for developing and deploying web apps, though, the pieces just didn't seem to add up.
$ uname -r