Install Emacs 24 in Ubuntu

CREDITS TO:
http://www.mikeyboldt.com/2011/11/30/install-emacs-24-in-ubuntu/

After reading several good things about emacs 24, I decided to give it a shot. A little googling led me to Damien Cassou’s emacs snapshot PPA. Simply ran the following:

sudo add-apt-repository ppa:cassou/emacs
sudo apt-get update
sudo apt-get install emacs-snapshot
emacs-snapshot

Everything works great so far, specifically email in mew, chatting with jabber.el, myorg files, and org2blog/wp. Played with the built-in ELPA package manager a little, and I really thing it will be nice to avoid manual package management.

Haven’t decided if/how often I’ll update my snapshot. Maybe until emacs 24 comes out in the Canonical packages? But then will I want to stay on the bleeding edge? Thoughts/suggestions/experiences?

mysqldump and load file the easiet way

The easiest explication for mysqldump and loading a database.

CREDITS TO:

http://forums.mysql.com/read.php?10,195091,195097

Read the manual on mysqldump, especially option --opt.  Also, check the 
section "Database backups", under "Solving common problems with MySQL". 
 
You can dump the database into a file using: 
 
  mysqldump -h hostname -u user --password=password databasename > filename 
 
you can restore the info to the database again using: 
 
  mysql -h hostname -u user --password=password databasename < filename

Using git stash

CREDITS TO:

http://ariejan.net/2008/04/23/git-using-the-stash

I bet the following has happened to you: you are happily working on a project and are in the middle of something. You are not ready to commit your changes, because you your tests don't pass yet. Then your client calls with a bug report that needs to be fixed right now. (You know how clients can be.)
So, what do you do? Throw away your current changes to make the patch? Checkout a clean copy of your project to make the changes? No! You just stash your changes away, and make the patch! Afterward you grab your changes back and continue work.
Git features The Stash, which is as much as a good place to store uncommitted changes. When you stash you changes, the will be stored, and your working copy will be reverted to HEAD (the last commit revision) of your code.
When you restore your stash, you changes are reapplied and you continue working on your code.
Stash your current changes

$ git stash save 
Saved "WIP on master: e71813e..."

List current stashes
Yes, you can have more than one!! The stash works like a stack. Every time you save a new stash, it's put on top of the stack.

$ git stash list
stash@{0}: WIP on master: e71813e..."

Note the stash@{0} part? That's your stash ID, you'll need it to restore it later on. Let's do that right now. The stash ID changes with every stash you make. stash@{0} refers to the last stash you made.
Apply a stash

$ git stash apply stash@{0}

You may notice the stash is still there after you have applied it. You can drop it if you don't need it any more.

$ git stash drop stash@{0}

Or, because the stash acts like a stack, you can pop off the last stash you saved:

$ git stash pop

If you want to wipe all your stashes away, run the 'clear' command:

$ git stash clear

It may very well be that you don't use stashes that often. If you just want to quickly stash your changes to restore them later, you can leave out the stash ID.

$ git stash
...
$ git stash pop

Feel free to experiment with the stash before using it on some really important work