So… Since I’ve started using git-svn at work, I do have an possibility to make things better now! The answer lies in client-side-hooks and git aliases (“custom commands”). First let’s write this as an simple bash script, that we’ll locate in the .git/hooks/ folder:
It’s a fairly simple script, so I wont bore you explaining it in detail – if in doubt, feel free to ask. We only need to place this script as “.git/hooks/pre-commit” and make it executable and git will take care of the rest for us. Oh and in case you’re wondering where that org.eclipse.jdt.core.prefs came from. It’s created by eclipse into the .settings folder when you check some option to “use formatter per project” – that’s the only time I had to fire up and click around in eclipse to get it’s formatter running “headless”. Ok, let’s check if it works…

Yup, you can agree or not with the formatting rules – but what matters is that the whole team decided on it and that we keep it consistent throughout the whole project. This hook will definitely help with this. :-) Step two for me was changing this into a git command, so that I wouldn’t launch eclipse each time I just do some quick local commiting. The solution is to drop the hook idea (although it’s quite nice) and create an custom git command. We do this by doing an alias like that:

git config --global alias.eclipse-formatter '!~/git-hook-eclipse-formatter'

The !command alias support is with us in git since 1.5.0 and it enables us to launch any program/script as an git command. Great, just what I wanted! Let’s now see what this command really did:

As you can see, adding an alias is as simple as adding it to your ~/.gitconfig or, if you want to setup the alias “per project”, to .git/config – pretty cool, ay? Also, this command will be included in bash-autocompletition suggestions! :-)

That’s it for today… happy hacking!

git mv oldname newname
        =
mv oldname newname
git add newname
git rm oldname

Note that last line, git rm oldname is what we fotgot to do in our example, thus git was seeing an just the “new file” version of our operation. One line wrong, yet very important :-) Let’s check if it works this way:

[ktoso@homunculus test]$ ls
jeden  typescript
[ktoso@homunculus test]$ git init .
Reinitialized existing Git repository in /home/ktoso/test/.git/
[ktoso@homunculus test]$ cat jeden
drugi pliczek
[ktoso@homunculus test]$ echo 'dwadwa' > dwa
[ktoso@homunculus test]$ cat dwa
dwadwa
[ktoso@homunculus test]$ git add .
[ktoso@homunculus test]$ git commit -m 'dodanie ich'
[master (root-commit) a430782] dodanie ich
2 files changed, 2 insertions(+), 0 deletions(-)
create mode 100644 dwa
create mode 100644 jeden
create mode 100644 typescript
[ktoso@homunculus test]$ git mv
dwa         .git/       jeden       typescript
[ktoso@homunculus test]$ git mv jeden nowy-jeden
[ktoso@homunculus test]$ git status
# On branch master
# Changes to be committed:
#   (use "git reset HEAD <file>..." to unstage)
#
#       renamed:    jeden -> nowy-jeden
#
[ktoso@homunculus test]$ mv
dwa         .git/       nowy-jeden  typescript
[ktoso@homunculus test]$ mv dwa nowe-dwa
[ktoso@homunculus test]$ git add nowe-dwa
[ktoso@homunculus test]$ git rm dwa
rm 'dwa'
[ktoso@homunculus test]$ git status
# On branch master
# Changes to be committed:
#   (use "git reset HEAD <file>..." to unstage)
#
#       renamed:    dwa -> nowe-dwa
#       renamed:    jeden -> nowy-jeden
#
[ktoso@homunculus test]$ echo "problem Solved... :-)"
problem Solved… :-)

Yup, it actually detects the renames proppery. Even more, it would detect an “copy” action (this works even easier):

[ktoso@homunculus test]$ cp nowy-jeden nowy-jeden-jeden
[ktoso@homunculus test]$ git add .
[ktoso@homunculus test]$ git status
# On branch master
# Changes to be committed:
#   (use "git reset HEAD <file>..." to unstage)
#
#       renamed:    dwa -> nowe-dwa
#       copied:     jeden -> nowy-jeden
#       renamed:    jeden -> nowy-jeden-jeden
#       modified:   typescript
#

I’m already converting all the presentations to MP4 files and they’ll be online soon I hope :-) Then I’ll also write an usual “review” as I always do with any confernce/meering. For now just a quick summary: An amazing attandee count, nice presentations and an very very nice crowd :-) Thanks a lot for all the talks, but let’s wair for my “review” with more informations about JC5… :-) (Oh, yes we’re allready planing JC6… ;-))

Hi there, below is the (horribly trashy and chaotic – as it was hacked up in about 2/3 hours) source for my Google Gmail Contextual Gadget.

It extends Gmail by parsing all links passed in an email, and if an github commit link is found it displays the diff for this commit. With coloring etc – just as github would. It’s really fairly easy to get this kind of things going, and if your working with Google Apps (using gmail in your domain etc) you can use this, and many more gadgets (though I didn’t find much of them really useful – that’s why I’ve written this one).

The source can be downloaded, and fixed (which I hopefuly will have time to do! As it’s a mess, let’s say, “proof of concept”): http://github.com/ktoso/GitHubDiff (It’s on the MIT license).

Read the full story to see instalation instructions as well as documentation links…

HOW TO INSTALL:
It can be installed by your own into gmail, if you’re running on Google Apps -just by creating an new Application on the Market and then adding it to your Account. If you’d like me to polish and publish this to the Google Enterprise Market – you’d have to fund me the publish fee, 100$… ;-)

DOCUMENTATION:
Contextual Gadgets: http://code.google.com/apis/gmail/gadgets/contextual/

jQuery – getJSON: http://api.jquery.com/jQuery.getJSON/
GitHub API – http://develop.github.com/p/commits.html

LICENSE:
The source is MIT licensed, feel free to use it as a base for your own projects etc. It’s nothing particularly well written etc ;-)

Enjoy github in your gmail – two amazing webapps in one… :-)

Our server “Kopiec” is somewhat online (running CentOS off course) – we’re able to start/stop if thanks to a tool that’s called “remote insight”, and I’ve put 3 databases on there. MariaDB, InfiniDB and a clean MySQL instalation. We’re somewhat having problems with TokuDB, but that’s going to be our 4th database of interest. If you want to keep track of our test’s you can take a look at: http://mysqlintegra.project13.pl/.

The first step in getting things tested is filling those db’s with some data, and I mean a LOT of data. So we hacked up a more or less quick and dirty python script called dbfiller (source code avaiable on github) that would simulate a very simple table generation scheme (people working on shifts and checking in when they’re finished or start some activity). If you’re interested, our task is specyfied in the /doc/Opis.pdf file (sorry, only in polish). After a few days it’s up and running and we’re moving on to filling up those databases with some gigabytes of data.

Next we’re going to write some SQL Views/Procedures and then we’ll use Apache JMeter to run some performance benchmarks of some interesting data storage engines.

PS: If you’re wondering about my GWT-Crossword project – yeah, it’s still actual, and I’ll get right on it when done with some of the stuff here.
PPS: Yes, an Linux powered phone AT LAST in my hands! The HTC HERO is comming to me really soon – never again shall I use a ShitOS like WindowsMobile 6.5.

Watch it on youtube to see useful annotations! If your still new to vim you might want to start with simple editing as shown here: http://www.youtube.com/watch?v=71YTkxUNwmg&NR=1

After executing this, click on a window you want to track X Window events in. You could “read” this command like this: “xev will track events in the window with the following -id, which we get by greping window information obtained by xwininfo” :-)

Ok, but why did I need such weird information? Well, I wanted to make a simple video showing vis, a vim plugin etc. But as it is always in vim, keypresses are essential – so I wanted to “show what i type” bigger :-) I’ll post it really soon btw… :-)

The command was posted on commandlinefu

You, brave Terminal Hero, shall kill -9 the daemon that has hidden itself in one of those files! We don’t know in which file you can find it though! We’re running out of time! The kingdom of GNU will be rm -rf‘d if you won’t make it in time!!! Luckily as a level 99 human root, have all the tools to find and exterminate the dragon in no time! So let’s get greping.

Ok, enough joking…This post is all about this one-liner:find . -exec grep "Onyxia" '{}' \; -print
It allows you to search all files (including sub directories) for the ones with the specified string inside them. It proved helpful to me as i had to get one *.php file from a photorec recovered bunch of files (some thousands of them…)…

Hope you had as much fun reading this as I had posting, and also that it might prove usefull to you. I found this on snipplr by the way, I really recommend this website!

PS: The title just sounds too awesome i think… If you didn’t get it, it’s about Onyxia’s Lair from World of Warcraft :-)

Oh man, that would take sooo much time...

Thanks goodness I’m not really keen on doing stuff the slow “not_smart” way, and the new server is a dedicated CentOS machine! :-) So, what did I do?

Yeah, no time wasted here!

There’s a lot of ways to accomplish this if you have shell access. You could:

1. wget -r --user=login --password='pass' ftp://admin:example.com/folder/

2. ncftp #normal ftp should also work the same way
   open ftp://example.com
   login
   pass
   mget -r folder

3. Yes, SCP is a great tool for this kind of situation, but i couldn’t use it since the old server didn’t have ssh acces :-( Here is how it could be used in such a situation:

   scp -r login@old.example.com:/home/folder login@new.example.com:/home/folder

I used the second method and am quite satisvied with it, as the servers did all the migrating i set up the database and did some other project related stuff… :-)

So… Which button is the confirm one…? Yup, the colors are screwed up! I guess that’s becouse they didn’t think that someone could have a dark OS skin that would also skin the buttons dark. Ah wel… Thankfully I use Firefox 3.5 and the Stylish extension! Using this extension you can override a websites CSS styles, and that’s just what i did. The following code can be used to fix all the input button colors:

Notice the !important at the end of the color attribute, that’s what forces this setting to be “final”. Let’s check if the changes fixed our problem…

Ahh… much better!