vjt

#!/bin/bash
# 
# Copy data from a Time Machine volume mounted on a Linux box.
#
# Usage: copy-from-time-machine.sh <source> <target>
#
# source: the source directory inside a time machine backup
# target: the target directory in which to copy the reconstructed
#         directory trees. Created if it does not exists.
#

olibob

#!/usr/bin/env ruby
# Author:       Olivier Robert
# Email:        [email protected]
# Date:         02/05/2013
# Version:      0.0.1
# Usage:        gsaMon <snmp agent>
# 
# Description:
# snmp query to a GSA appliance:
# => system.temperature.temperatureHealth Integer, Read-only  Temperature status:

freegenie

after_fork do |server, worker|
  log_path = Rails.root.join('log',"#{Rails.env}.#{worker.nr}.log")

  new_logger = Logger.new(log_path)
  new_logger.level = Logger::INFO

  Rails.logger.flush
  Rails.logger.close
  Rails.logger = Rails.application.config.logger = ActiveSupport::TaggedLogging.new(new_logger)

unak

* Only the releases of the stable versions are listed in principle.  The releases of the unstable versions especially considered to be important are indicated as "not stable."
* The branches used as the source of each releases are specified, and the branching timing of them are also shown.  BTW, before subversionizing of the repository, the term called "trunk" was not used, but this list uses it in order to avoid confusion.
* In order to show a historical backdrop, big conferences (RubyKaigi, RubyConf and Euruko) are also listed.  About the venues of such conferences, general English notations are adopted, in my hope.
* ruby_1_8_7 branch was recut from v1_8_7 tag after the 1.8.7 release because of an accident.
* 1.2.1 release was canceled once, and the 2nd release called "repack" was performed.  Although there were other examples similar to this, since the re-releases were performed during the same day, it does not write clearly in particular.
* Since 1.0 was released with the date in large quantities, the mi

antirez

#!/usr/bin/tclsh8.5
#
# Usage: unmerged branch1 branch2

proc getlog branch {
    lrange [split [exec git log $branch --oneline] "\n"] 0 100
}

proc diff {title c1 c2} {
    puts "\n$title"

DAddYE

#!/bin/sh

##
# This is a script with usefull tips taken from:
#   https://github.com/mathiasbynens/dotfiles/blob/master/.osx
#
# Run in interactive mode with:
#   $ sh -c "$(curl -sL https://raw.github.com/gist/2108403/hack.sh)"
#
# or run it without prompt questions:

dansimau

#!/bin/bash
#
# Converts LDIF data to CSV.
# Doesn't handle comments very well. Use -LLL with ldapsearch to remove them.
#
# 2010-03-07
# [email protected]
#

# Show usage if we don't have the right params

mnutt

Instrument Anything in Rails 3

With Rails 3.0 released a few weeks ago I've migrated a few apps and I'm constantly finding useful new improvements. One such improvement is the ability to log anything in the same way that Rails internally logs ActiveRecord and ActionView. By default Rails 3 logs look slightly spiffier than those produced by Rails 2.3: (notice the second line has been cleaned up)

Started GET "/" for 127.0.0.1 at Mon Sep 06 01:07:11 -0400 2010
  Processing by HomeController#index as HTML
  User Load (0.2ms)  SELECT `users`.* FROM `users` WHERE (`users`.`id` = 3) LIMIT 1
  CACHE (0.0ms)  SELECT `users`.* FROM `users` WHERE (`users`.`id` = 3) LIMIT 1

Rendered layouts/_nav.html.erb (363.4ms)

endolith

ּ_בּ
בּ_בּ
טּ_טּ
כּ‗כּ
לּ_לּ
מּ_מּ
סּ_סּ
תּ_תּ
٩(×̯×)۶
٩(̾●̮̮̃̾•̃̾)۶