GiT derken ME ekleyemedım sonuna ...
nasıl sızladı ıcım...
kan bıle akmadı dıslerımın bırlestıgı dudaklarımdan
tıtreyen elımde bır sıgara
nedenlı ama bılıncsız atılan yumruklarım kaldı duvarlarda ...

shawin...:(

NOTA: Que esten usando la ultima de las versiones, quiere decir que van a tener MAS EFECTOS (es decir, MAS PLUGINS) pero tambien que este se puede comportar un poco inestable.

Para instalar Compiz-fusion desde su GIT, lo que vamos a hacer es tomar ventaja de una utilidad muy linda escrita en python, que se llama FusionBuild. que se va a encargar por nosotos de descargar los archivos correspondientes. Y esta de mas decir que si quieren agregar algun parametro para OPTIMIZARLO y hacer que "ande mas rapido" o "consuma menos memoria" van a tener que agregarlo al Makefile, y eso tambien va a depender de su hardware y de la distro que esten usando :). De cualquier manera no es complicado, y quisiera saber si ustedes quisieran que ponga un tutorial sobre eso.

Bueno, para comenzar vamos a tener que descargar el codigo fuente (como siempre, tienen un tar.gz o un tar-bz2) y descomprimirlo.

Para descargarlo, pueden hacerlo desde este enlaze: (NOTA: Si estan en una consola y les resulta comodo, es altamente recomendable que usen WGET, porque es rapido, es efectivo, es a mi forma de verlo uno de los mejores gestores de descarga (menos para rapidshare/megaupload/ya_comprenden_la_onda :P)

Descarguen Fusion-build desde aca: http://fusionbuild.wordpress.com/download/ (seleccionen la ultima version, o al menos la ultima estable)

Una vez hecho esto,lo descomprimen, y lo ejecutan en una consola o con algun launcher usando:

python fusionbuild (Obviamente especificando delante de fusionbuild el directorio donde lo pusieron)

Por ejemplo, si descargaron el archivo en ~/fusionbuild y lo descomprimieron, van a tener una carpeta ahi dentro, y dentro de esa va a estar el script de python que necesitan.

NOTA: ~/ es lo mismo que el HOME de tu usuario, pueden ver el contenido de ~/ haciendo echo $HOME.

Despues de eso, tienen que configurar su Xorg.conf (en /etc/X11/xorg.conf por lo general) y agregar la categoria Composite, no olviden usar sus drivers / modulos con aceleracion 3D porque los otros no les va a funcinoar, no soportan esa clase de cosas, pero eso, ya va para otra entrada :P, Si alguien quiera que escriba un tuto para alguna distro en especifico (como Gentoo, Oh! Mi amado Gentoo!) me avisan :)

Lo que tienen que agregar (al final de su xorg.conf) es:

Section "Extensions"
Option      "Composite"   "enable"
EndSection

Ademas, en este sitio web pueden encontrar algunas cosas que pueden reducir un poco el uso de memoria de compiz-fusion aunque tambien reduzcan su integracion:

http://wiki.compiz-fusion.org/Installation

Les recomiendo que visiten su sitio y el de su distro para mas informacion, pero no hay problema en que me la pidan.

Eso ha sido, todo, discupen por escribirlo a las apuradas, este es el primer post y espero que les guste ;)

ESPERO MUCHO FEEDBACK! Asique posteen comentarios!

While I was trying to install a taxprogram I think I messed up my /usr, got all sorts of 'Permission Denied' so I decided to reinstall Gentoo.
Which didn't go fast enough because I needed my laptop for school use. So I decided to install Sabayon, but that didn't go so well. So in the end I decided to install fedora 9 which runs nice and smooth.
But I longed back for Gentoo, that when I installed KVM and I started with my Gentoo install.

I used the stage3 from www.funtoo.org/linux and the portage tree from www.github.com/funtoo
At the moment I intend to create a solid base-system with all my needs and create a stage4. I hope Daniel Robbins his stage-create-tool a.k.a. Metro is finished before I get to that stage :P

Anyway I'm just done with getting rid of circular dependencies. I'm now rebuilding the system with enabled USE-flags
After that I'll review all the USE-flags and adjusting /etc/make.conf || /etc/portage/package.use accordingly
And when I'm done rebuilding those packages I'll move to emerging X

Sounds like I'm not done yet.. And to make it more interesting it's all in kvm.

Let's say I originally created my git repository on the laptop:

david@laptop$ mkdir ~/repo
david@laptop$ cd !$
david@laptop$ git init
david@laptop$ echo "hello world" > hello.txt
david@laptop$ git add hello.txt
david@laptop$ git commit -m 'Added hello world'

To continue to work on my desktop I'll just clone the repository on my desktop:

david@desktop$ git clone ssh://192.168.0.42/home/david/repo
david@desktop$ cd repo

Let's say I do some commits on the desktop now:

david@desktop$ for i in $(seq 5); do echo $i >> hello.txt; \
git commit -am "added $i"; done

Now I can simply push them back to the laptop:

david@desktop$ git push

Let's go back to the laptop now:

david@laptop$ git status
# On branch master
# Changes to be committed:
#   (use "git reset HEAD ..." to unstage)
#
#	modified:   hello.txt
#

We notice it say's the file has been modified. The reason is that the previous
push from the laptop didn't update the working directory, as a diff shows:

david@laptop$ git diff --cached
diff --git a/hello.txt b/hello.txt
index 1c8a100..3b18e51 100644
--- a/hello.txt
+++ b/hello.txt
@@ -1,6 +1 @@
 hello world
-1
-2
-3
-4
-5

So we'll just checkout the version that has been pushed previously:

david@laptop$ git checkout -f HEAD

Let's do some work on the laptop:

david@laptop$ git checkout -b dev
david@laptop$ echo "this is a new file" > new.txt
david@laptop$ git add new.txt
david@laptop$ git commit -m 'Added new file'
david@laptop$ git checkout master
david@laptop$ echo "6" >> hello.txt
david@laptop$ git commit -am 'Added 6'

Now to push those changes to the desktop we have to add the desktop as a remote.

david@laptop$ git remote add desktop ssh://192.168.0.12/home/david/repo
david@laptop$ git push desktop

This will push the latest changes in the master branch. To push the dev branch:

david@laptop$ git push desktop dev

Now let's rebase dev onto master:

david@laptop$ git rebase master dev

With the rebase we went from:

hello -- added 1 -- added 3 -- added 4 -- added 5 -- added 6   <-- master
                                              \
                                              added new file  <-- dev

To:

hello -- added 1 -- added 3 -- added 4 -- added 5 -- added 6   <-- master
                                                         \
                                                         added new file  <-- dev

If we now try to push from the laptop to the desktop it will fail:

david@laptop$ git push desktop dev
david@192.168.0.12's password:
To ssh://192.168.0.12/home/david/repo
 ! [rejected]        dev -> dev (non-fast forward)
error: failed to push some refs to 'ssh://192.168.0.12/home/david/repo'

The reason is that it is not a fast forward push, so what we have to do to push
anyway is force the push:

david@laptop$ git push desktop dev -f

In summary, if you have done some changes which result in a non-fast forward
push you can push those change anyway using the '-f' switch.

WARNING: Non-fast forward pushes are disabled by default to prevent you from
losing changes that are on the remote repository and that are not in your local
repository. If you do accidentally lose some changes on the remote end, you can
log on to the remote machine, use git reflog to find the commit that was the
HEAD before the forced push was executed and establish that commit as the HEAD
again using git reset --hard.

Now let's see what happens if you try to do a non-fast forward pull. First
we'll have to do some changes that will result into a non-fast forward merge.
For instance, let's squash some commits using interactive rebase:

david@laptop$ git checkout master
david@laptop$ git log --pretty=oneline
3003e24db3933cdcf0b337efee105bb8d5fab162 Added 6
addeee530032c74354b119fd0afd5370ebcec744 added 5
94c3719981b10553b3dba4d34c56c4c383769bee added 4
8ed90f1eb2bafc66a238b2fff3a85e579f782b3c added 3
c499db8d72aab61eb275d38df72bcaddb3a5e263 added 2
5fd3b26ffcdd611e6f58e5ec4a7ed8ce34ffe546 added 1
0efc99fff3e258961c321b529930bc56c5d91c39 Added hello world
david@laptop$ git rebase -i master~6

Your editor will be opened with the following contents:

pick 5fd3b26 added 1
pick c499db8 added 2
pick 8ed90f1 added 3
pick 94c3719 added 4
pick addeee5 added 5
pick 3003e24 Added 6

# Rebase 0efc99f..3003e24 onto 0efc99f
#
# Commands:
#  pick = use commit
#  edit = use commit, but stop for amending
#  squash = use commit, but meld into previous commit
#
# If you remove a line here THAT COMMIT WILL BE LOST.
# However, if you remove everything, the rebase will be aborted.
#

Now let's squash some commits:

pick 5fd3b26 added 1
pick c499db8 added 2
pick 8ed90f1 added 3
squash 94c3719 added 4
squash addeee5 added 5
squash 3003e24 Added 6

# Rebase 0efc99f..3003e24 onto 0efc99f
#
# Commands:
#  pick = use commit
#  edit = use commit, but stop for amending
#  squash = use commit, but meld into previous commit
#
# If you remove a line here THAT COMMIT WILL BE LOST.
# However, if you remove everything, the rebase will be aborted.

Save and quit and your editor will open again for a new commit message. Edit
the new commit message, save and quit. Now the log should look similar to this:

david@laptop$ git log --pretty=oneline
857596e692c7fd98d019dae2630dc320f5c95177 added 3 added 4 added 5 Added 6
c499db8d72aab61eb275d38df72bcaddb3a5e263 added 2
5fd3b26ffcdd611e6f58e5ec4a7ed8ce34ffe546 added 1
0efc99fff3e258961c321b529930bc56c5d91c39 Added hello world

Now let's go back to the desktop and see what happens if we do a pull now:

david@desktop$ git co -f master
david@desktop$ git pull
david@desktop$ git log --pretty=oneline
c4b80bae8d6a86373fac45e16c89608a6009e8fc Merge branch 'master' of ssh://192.168.0.42/home/david/repo
857596e692c7fd98d019dae2630dc320f5c95177 added 3 added 4 added 5 Added 6
3003e24db3933cdcf0b337efee105bb8d5fab162 Added 6
c499db8d72aab61eb275d38df72bcaddb3a5e263 added 2
addeee530032c74354b119fd0afd5370ebcec744 added 5
5fd3b26ffcdd611e6f58e5ec4a7ed8ce34ffe546 added 1
94c3719981b10553b3dba4d34c56c4c383769bee added 4
8ed90f1eb2bafc66a238b2fff3a85e579f782b3c added 3
0efc99fff3e258961c321b529930bc56c5d91c39 Added hello world

As you can see the pull doesn't rewrite the history, i.e. the log looks
different now on the laptop and on the desktop. I find that confusing, I'd
prefer having the same commit history on all my machines. Let's undo that last pull:

david@desktop$ git reset --hard HEAD^
david@desktop$ git log --pretty=oneline
3003e24db3933cdcf0b337efee105bb8d5fab162 Added 6
addeee530032c74354b119fd0afd5370ebcec744 added 5
94c3719981b10553b3dba4d34c56c4c383769bee added 4
8ed90f1eb2bafc66a238b2fff3a85e579f782b3c added 3
c499db8d72aab61eb275d38df72bcaddb3a5e263 added 2
5fd3b26ffcdd611e6f58e5ec4a7ed8ce34ffe546 added 1
0efc99fff3e258961c321b529930bc56c5d91c39 Added hello world

What I'd like to do is something equivalent to a push --force but with a pull.
The solution is using the plus sign with pull:

WARNING: The same caution as to a push --force applies, you can loose changes
that are on your local repository but not on the remote repository when using a
pull with the plus sign. Although, like in the previous warning, you can
probably use git reflog and git reset --hard to get those changes back.

david@desktop$ git pull origin +master:master

The first master references the remote master branch and the second references
the local master branch. If we now look at the commit history we can see that
it is the same as on the laptop:

david@desktop$ git log --pretty=oneline
857596e692c7fd98d019dae2630dc320f5c95177 added 3 added 4 added 5 Added 6
c499db8d72aab61eb275d38df72bcaddb3a5e263 added 2
5fd3b26ffcdd611e6f58e5ec4a7ed8ce34ffe546 added 1
0efc99fff3e258961c321b529930bc56c5d91c39 Added hello world

In summary, the equivalent pull operation to a "git push --force" is a pull
using the plus sign.

Finally one more WARNING: do not force push to repositories from which other
people have already pulled as that may cause problems for them. See
problems with rewriting history in the git manual.

While searching around the internet, I came across this website that it actually really good. I, myself, am someone who loves to keep up on gaming news. Usually I like to use a few independent gaming news sites, and Kotaku. Today I present to you a gaming website that hasn't really been around that long. It is "Powered by Sci-Fi". Check it out, as it updates hourly. Great site, strongly suggest you bookmark it.

From first impression, I like Bazaar, here's why:

• It's written in Python.
• Furthermore, because it is written in Python, installation is a breeze: `easy_install bzr`
• It has similar terminology to SVN. That means lower learning curve.
• Bazaar has really good storage compression. See the comparisons that others have done below.

Bit of History:

Martin Pool started Bazaar when he was just hired by Canonical, ltd.

List of Projects using Bazaar[link]:

Below is not the complete list, see link above for more.

• Bugzilla@Mozilla
• GNU Mailman
• MySQL
• Squid - Caching Proxy project. It caches frequently visited web pages.

Others have attempted to compare Bazaar vs Git:

• http://blog.jozilla.net/2006/03/03/bzr-versus-git/
• http://laserjock.wordpress.com/2008/05/08/git-and-bzr-historical-performance-comparison/

References:

• Bazaar Main Page
• John Arbash Meinel (Bazaar's developer) blog
• Wikipedia - Bazaar
• Wikipedia - Git
• Wikipedia - Mercurial

To change the default merging behavior in git, you run

git config --global merge.tool toolname

To see the list of available tools, type

git mergetool

Most of the tools that git understands are unix-y. There is one OS X tool on the list: opendiff, which launches the FileMerge tool. But honestly, I've never been that impressed with FileMerge's merge algorithm.

Fortunately, xxdiff is a pretty good tool, and it's available as a Darwin port. So, assuming you already have your OS X box set up to install ports, you can have this as your default git merge user interface by running:

sudo port install xxdiff
git config --global merge.tool xxdiff

Now files needing a merge will open in the xxdiff user interface - which is an ugly XWindows thing, but it's powerful. I'd love to see git hook up to something like Araxis Merge or Changes (when their 2.0 version with 3-way merge comes out), but I'm not nearly motivated enough to hack around in the git source yet.

nna (10/4/2008 11:44:03 AM): :D

teh ita (10/4/2008 11:44:06 AM): udah puny y?
nna (10/4/2008 11:44:21 AM): blom teh,,
nna (10/4/2008 11:44:30 AM): buku apa sih teh?pnasaran.
teh ita (10/4/2008 11:44:36 AM): yeee
teh ita (10/4/2008 11:44:42 AM): unduhlah
nna (10/4/2008 11:44:51 AM): dimilis kan?
nna (10/4/2008 11:44:58 AM): na baru join milisnya kemaren,,
teh ita (10/4/2008 11:44:59 AM): trilogi yusuf ardiansyah
teh ita (10/4/2008 11:45:09 AM): ho oh
nna (10/4/2008 11:45:17 AM): bisa dimana downloadnya?
nna (10/4/2008 11:45:31 AM): ntar deh,
teh ita (10/4/2008 11:45:33 AM): d milis
teh ita (10/4/2008 11:45:44 AM): okeh
nna (10/4/2008 11:45:51 AM): na cek,,,moderatornya da ngeapprove apa blom,
teh ita (10/4/2008 11:45:59 AM): akan kuteror terus dirimu,ok?
nna (10/4/2008 11:46:05 AM): oke
nna (10/4/2008 11:46:12 AM): teh aku teh lagi sakit
nna (10/4/2008 11:46:21 AM): pusing..pilek,,lemas,,banyak PR.
teh ita (10/4/2008 11:46:21 AM): ehehehe
teh ita (10/4/2008 11:46:28 AM): aduh,ina
nna (10/4/2008 11:46:40 AM): sekarang aja ditinggal dirumah ama yang laen,
teh ita (10/4/2008 11:46:49 AM): makany jgn lngsung bls dndam
nna (10/4/2008 11:46:55 AM): heu
nna (10/4/2008 11:46:58 AM): pilekk..
nna (10/4/2008 11:47:25 AM): blom di approv ma moderatornya,
teh ita (10/4/2008 11:47:46 AM): yah
teh ita (10/4/2008 11:48:39 AM): sabar y

dan pada siangnya..status YM na gini.

karenakitakeluarga

Membership is Pending

19 New Messages

3 New Members

22 New Files

niatnya sih, ada anak G yang tau siapa moderatornya trus bisa berbaik hati ngasi tau moderatorny karena na yakin..anak G kan baikbaik..

eh.ternyata ada yang membantuu.

teh shinta (10/4/2008 4:10:47 PM): Statusny knp tuh na??
nna (10/4/2008 4:11:09 PM): yah,syapa tau ada yang kenal sama moderatornya karenakitakeluarga..
nna (10/4/2008 4:11:20 PM): karena,,na mau download sesuatu disana..
nna (10/4/2008 4:11:22 PM): tetehh..
nna (10/4/2008 4:11:28 PM): mohon maaf lahir bathin yaa.
teh shinta (10/4/2008 4:11:37 PM): Ke kak adit aja atuh
nna (10/4/2008 4:11:37 PM): teteh ada Fb yaa?mau add dong,
teh shinta (10/4/2008 4:11:58 PM): Ada si.. Tp gk prnh diapa2in tuh
nna (10/4/2008 4:12:06 PM): na add yaa.
nna (10/4/2008 4:12:08 PM): namanya apa,
teh shinta (10/4/2008 4:12:14 PM): Sama2 y,,mhn maaf lahir batin jg
teh shinta (10/4/2008 4:12:43 PM): Shinta.. xxxxxxxxxxx@yahoo.com
teh shinta (10/4/2008 4:13:14 PM): Mw download apa emgny? Pnting bgt gk?
nna (10/4/2008 4:13:36 PM): hmm.
nna (10/4/2008 4:13:38 PM): itutuh
nna (10/4/2008 4:13:39 PM): GIT
nna (10/4/2008 4:13:48 PM): Gamais Training apaa gtu..
teh shinta (10/4/2008 4:14:16 PM): Oo..
teh shinta (10/4/2008 4:14:26 PM): Mw pake akun saya aj?
nna (10/4/2008 4:14:35 PM): wah.
nna (10/4/2008 4:14:40 PM): jadi ga enak,
teh shinta (10/4/2008 4:15:26 PM): Gpp koq..
teh shinta (10/4/2008 4:15:27 PM): Gmn? Mw gk?
nna (10/4/2008 4:16:03 PM): boleh deh.
nna (10/4/2008 4:16:06 PM): hehe.
teh shinta (10/4/2008 4:16:31 PM): Id : XXXXXXXXXXXX
teh shinta (10/4/2008 4:16:37 PM): Pass : XXXXXXXXXXXX
nna (10/4/2008 4:17:43 PM): fbnya dah di add teh,,

wah,,alhamdulillah,,heuheu.

bisa juga di doenload walaupun dengan akun orang,,

dan na lagi YM ma seorang akhi,

nna (10/4/2008 4:17:11 PM): itu ikutan GIT ga?
XXXXXs (10/4/2008 4:17:41 PM): apa tuh??
nna (10/4/2008 4:17:53 PM): Gamais Training apaa gtu..
nna (10/4/2008 4:17:56 PM): ikutan gih,
nna (10/4/2008 4:18:15 PM): kya klompok2 gtu.
nna (10/4/2008 4:18:28 PM): mau ikut klopok aku?
nna (10/4/2008 4:18:34 PM): na klompok 2.
nna (10/4/2008 4:18:43 PM): na klompok 4 deng,
nna (10/4/2008 4:19:01 PM): PJnya teh ita sama kak Tusi
nna (10/4/2008 4:19:16 PM): klo kelompok 2 pjnya kak ryan TM,
nna (10/4/2008 4:19:21 PM): gtugtu lah,
nna (10/4/2008 4:19:30 PM): kyanya emang publikasinya kurrang ya.
XXXXXs (10/4/2008 4:19:36 PM): ma sapa ajah??
nna (10/4/2008 4:19:40 PM): gatau na juga
nna (10/4/2008 4:19:59 PM): dan na ceritanya blom masuk milis karenakitakeluarga
nna (10/4/2008 4:20:06 PM): padahal ada tugas liburan,
XXXXXs (10/4/2008 4:20:29 PM): owh
XXXXXs (10/4/2008 4:20:37 PM): ga kedengeran tuh
XXXXXs (10/4/2008 4:20:41 PM): ntar liat deh
XXXXXs (10/4/2008 4:20:50 PM): gi sibuk diospek nih

|
|

ngasih ke si akhi itu filefile GIT
|
XXXXXs (10/4/2008 4:56:42 PM): tapi kalo mw daftar gimna??
nna (10/4/2008 4:58:00 PM): kmu maunya ikut klompok mana,,
nna (10/4/2008 4:58:04 PM): sms aja ketuanya
XXXXXs (10/4/2008 5:00:49 PM): kelompok 6 kalo jadi
nna (10/4/2008 5:01:49 PM): sip
XXXXXs (10/4/2008 5:02:14 PM): sipp

dan...

asik..asik..baca2 filenya,,tersadar..ingin mencari teman seperjuangan..

hmm..

then..

OK!

hah?yang lain kmanaa...

temann...temani aku..

Why GIT have been chosen to support our version control needs?

• Failure in development server will not block our work
• Access to history is very fast (it's stored on every working copy)
• I used to work during flight, GIT supports all VCS operations off-line (commit, diff, etc.)

The hard thing about GIT is that it may confuse beginners. If you are one, remember:

• Always use git diff HEAD instead of git diff
• Always using git commit -a instead of git commit

Some of this gotchas have been addressed by some GIT interfaces, but they are deprecated now.

In order to ease GIT (and earlier, CVS) usage we introduced additional Makefile targets that handle typical source control tasks.

Examining working copy.

make st shows current working copy state with all local branches and current selected branch:

    st:
        git branch
        git status -a | cat

(cat simply remove pager call). make di shows differences between last commited version and working copy:

    di:
        git diff HEAD

Locally stored history (few last commits) can be inspected by make ch:

    ch:
        git log --pretty=oneline -15 | cat

We are using topic branches strategy to develop software, so switching brach (make sb) is a very common operation:

    sb:
        @read -p "name of existing branch to switch to [a-z_0-9]+: "\
            branch_name;\
        git checkout $$branch_name;

Local commits

If we have some changes uncommitted in working copy we can commit them now:

    commit: di st
        git commit -a

Above command shows current changes to be committed (di) and state of a repository (st) then allows to enter comment.

Going remote

Lets synchronize our working copy with central repo (without locally unmodified changes): make sync:

    sync:
        -git pull $(REPO) +`git branch | awk '/^\*/ {print $$2}'`
        git push $(REPO) `git branch | awk '/^\*/ {print $$2}'`

It downloads curent branch from central serwer (this operation can fail when no branch exists yet, so we ignore errors here by "-" character) and pushes unsynced commits made.

Ich war auf der Arbeit wie immer fleißig am Programmieren und irgendwie ist das Thema aufgekommen, dass ich doch so laut Tippen würde. Ich glaube man könnte mir tatsächlich eine alte mechanische Schreibmaschine unter die Finger legen und würde einfach weiter klimpern.

Daraufhin habe ich jedenfalls entgegnet, dass die Kollegen lieber froh sein sollten, dass ich keine Schreibmaschinensounds, wie im standard ICQ Client, an hätte.

Aus Spass suchte ich nach einem Client unter X der so etwas kann und habe leider nichts gefunden. Ich konnte es kaum verstehen, wo dieses Feature doch derart essenziell ist.

Wie dem auch sei bin ich immer froh wenn ich etwas finde dass es noch nicht gibt - wie oft ist es vorgekommen das ich der Meinung war eine Tolle Idee zu haben und irgendwann feststellen musste, dass es das (leider) schon längst gab. (So wie Instant Messaging über IRC http://www.bitlbee.org/)

Somit habe ich mich nun dran gemacht einen Schreibmaschinensound-Effekt Client für X zu schreiben. Passender weise heißt dieser Annoyme.

Es hat sich herausgestellt, dass das globale empfangen der Tastatur Event nicht ganz so einfach ist wie erwartet aber dank einem funktionierenden XEvIE nun doch möglich ist.

Ich habe mir für das Projekt in C++ einen Account bei github erstellt und werde es darüber pflegen. Ich sehe es als Gelegenheit etwas mehr Erfahrung mit git zu sammeln. Bisher macht es einen relativ benutzerfreundlichen Eindruck.

http://github.com/dedeibel/annoyme/tree/master

sh configure_insoshi_local.sh <GitHub account name>

I got the following error:
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
error: failed to push to 'git@github.com:windhood/stage.git'

To solve this error, you need do as following:

$ cd ~/.ssh
$ ssh-add id_rsa
id_rsa is the public key name file you used for your github

|-------Twelve Inches------|

How much for one rib?

Pimp of the Year

Unfortunately, the practice of tagging releases isn't as common as it should be. Tags are pretty much just aliases for commits, though they can be annotated and even GPG signed (so, for example, no one can fake a Linux kernel tag by Linus). Part of that may be that Git doesn't push tags by default.

But pushing a tag is easy, just add the --tags parameter to the push and it'll push all your tags.

git push --tags origin master

Or, if you only want to push a single tag, you can push the tag directly.

git push origin mynewtag

Unlike Subversion tags, these won't create whole new copies of the repository that can accidentally be committed to.

Tags are very useful when dealing with different releases of a project and you find yourself wondering what code was like in a previous version or a version past what you're currently using. Being able to browse the source directly on a site like GitHub is very valuable, but having to look up the what commit has a comment like "bumping version" is annoying and time consuming. Not to mention that it's more difficult to trust any old comment. 

So please tag your releases. It doesn't take a lot of effort and makes life easier for people using your project.

red
green
   commit
refactor
   commit

That extra "commit" at the green bar captures the safe state, in case I get distracted by the kids or forget to take my medication. It also shares that working code with the rest of the team, which in turn makes sure I get feedback on whether it builds. And that also makes sure those tests get run more frequently and outside of my environment sooner.

Recently I've been learning to use Git (which I like a lot, although some of the differences from Subversion stil baffle me a little). Anyroadup, with Git I can get even more safety from the process:

red
   commit
green
   commit
   push
refactor
   commit
   push

The extra "commit" at the red bar is local to my repository. It means I can "stop on a red bar", as used to be recommended in the early days of TDD, and yet still have all my code checked in.

I wonder whether I'm becoming more paranoid as Old Age now has me in its grip...

#!/bin/sh

$EDITOR `git status|grep unmerged|cut -d ':' -f2`

  o---X   <-- master
   \
    b1---b2---b3---b4   <-- b

Now we urgently need the commits b1 and b3 in master, but not the remaining commits in b. So what we do is checkout the master branch and cherry-pick commits b1 and b3:

$ git checkout master
$ git cherry-pick "b1's SHA"
$ git cherry-pick "b3's SHA"

The result would be:

  o---X---b1'---b3'   <-- master
   \
    b1---b2---b3---b4   <-- b

Let's say we do another commit on master and we get:

  o---X---b1'---b3'---Y   <-- master
   \
    b1---b2---b3---b4   <-- b

If we would now merge branch b into master:

$ git merge b

We would get the following:

  o---X---b1'---b3'---Y--- M  <-- master
   \                     /
     b1----b2----b3----b4   <-- b

That means the changes introduced by b1 and b3 would appear twice in the history. To avoid that we can rebase instead of merge:

$ git rebase master b

Which would yield:

  o---X---b1'---b3'---Y   <-- master
                       \
                        b2---b4   <-- b

Finally:

$ git checkout master
$ git merge b

gives us:

  o---X---b1'---b3'---Y---b2---b4   <-- master, b

Reference: http://kerneltrap.org/mailarchive/git/2008/7/23/2648694

Here's Robben with the Yellowjackets in 1979.

penggunaan command diff yang biasa kita dapatkan dari *nix/linux command ini bisa juga kita dapatkan dengan Ruby, mungkin bagi yang belum tahu sempat terfikir untuk memakai javascript anu (hah? javascript) atau bahkan akses ke system ataupun backtick -_-

Berikut link link ke resource tsb, selamat menikmati!

Situsnya, Sedot source codenya dalam format kompresan zip, hm.. udah, biasanya dari sana kalo dilirik mustinya kalo orang Ruby udah jelas, ndul.

Tapi berhubung ada yang lagi manja dan pingin dimanja trus lagi bernafsu manja (anying brengsek), nih tambahan link linknya.

Riff Active Record diff plugin di Pull Monkey huh dasar monyet!, keterangan soal riff plugin di wikinya rails ah ternyata lagi lagi ke wiki rails juga ya, trus sama ini postingan di blognya si juixe

Udah, mo mbalik semedi lagi.

Ako feat. Rapizm Çagla - Ask-i ilan
Corrupt & RapizmCagla - Hiciv Olsun
Rapizm Çağla feat Fieber,Hayki,Kaplan,Garez,Aycha- 6 ÇEKER
Rapizm Çağla feat Medusa - Duygu Sallarım
Rapizm Çağla feat Medusa - Git
Rapizm Çağla feat Medusa - Kız Kıza
RapizmCagla - Ala Turka
RapizmCagla - Sirlari Anla
RapizmCagla - Sonunu Yazdim
RapizmCagla - U‡uruma Dogru
RapizmCagla feat Enkaz - Kasarli Baby
RapizmCagla feat Izah - Melankoli
RapizmCagla feat Medusa - Marifetini Goster

TIKLA İNDİR

01. Medusa - Intro
02. Medusa - Medusa'nın Ruhuna
03. Medusa ft. Samuray - Umutlarım Tükendi
04. Medusa - Çöl
05. Medusa ft SiRmC & EmzE - Herşeyin Sebebi Var
06. Medusa - Medusa
07. Medusa - Saklanırım
08. Medusa - Şeytan Kulağına
09. Medusa - Havadis
10. Medusa - Git
11. Medusa - Antika Bedenler

TIKLA İNDİR

Hayki&Funye-Uyuyorum Bi Dakka!!!(ihtilal record's)
ihtilal ft.aycha-cellat oglu cellat
ihtilal ft.baskan-style wars
ihtilal ft.darp&singaf&fieber-mc merasimi
ihtilal ft.itaat&radyasyon&rasit&aycha&surveyan-git isine
İhtilal Ft.medusa&rapizm cagla-ghetto tayfalar
ihtilal ft.Saladin-Ter Döker Her Böcek
ihtilal ft.singaf&logic&erdem&itaat-alın yolunuzu
ihtilal(garez&hayki)-yak kendini
ihtilal-cıkıs
ihtilal-giriş(yas)
ihtilal-HEMOFİLİ-2004
ihtilal-kuralda biziz yasada
ihtilal-saygı duy
Kaplan feat.Sürveyan - Canını Yakarım (Hardcore Version)

TIKLA İNDİR

Ronin is a platform for information security and data-exploration tasks. Ronin harnesses the elegance of Ruby (one-liner convenience methods, sparse monkey-patching, meta-programming, Domain Specific Languages (DSL) and duck-typing) to provide the user with a robust API, an extendable command-line utility and a customized IRB console.

Ronin is considered a platform and not a framework, since it has the ability to install Overlays of code (think extensions) and data (think exploit/shellcode repositories) from any SubVersion (SVN), Git, CVS or Rsync repositories, which are then integrated into Ronin's environment. The ability to install 3rd party code or data from any common source-code repository using just a URI is what makes Ronin decentralized.

Ronin is not bloated either, most of it's functionality is divided between various libraries which can be selectively installed by the user. These libraries allow the user to choose what functionality they need from Ronin. Ronin currently provides the following libraries:

• Ronin SQL - Provides SQL Injection tests, exploitation methods and a DSL for generating complex SQL Injection statements.
• Ronin PHP - Provides PHP Local File Inclusion (LFI) and Remote File Inclusion (RFI) tests, fingerprinting, exploitation methods and a custom PHP Remote Procedure Call (RPC) server which can injected via RFI vulnerabilities.
• Ronin Dorks - Provides a simply API for performing common or even custom Google Dorks.
• Ronin Exploits - Provides an API for defining Exploits or Payloads which can also be distributed over the previously mentioned Overlays and cached by Ronin for later use.

Ronin is packaged as a RubyGem and can be downloaded here. To install Ronin using RubyGems, simply run the following command:

$ sudo gem install ronin

Documentation for Ronin and it's libraries can be found here. If you have further questions there's also a FAQ for Ronin.

Update 2: I have recently published a HOWTO covering Ronin's convenience methods and how to perform everyday tasks in the Ronin Console (such as owning web-servers).

Update 1: An astute reader of this blog pointed out that R'epertoire 0.1.2, which is required by Ronin, was not yet released as a RubyGem on rubyforge.org. This issue has been corrected and R'epertoire 0.1.2 is now available for download.

Also expect a release of the Ronin Exploits soon (I'm in the process of adding the beginnings of Vulnerability Taxonomy to the Exploit base-class).

Can anyone out there point me in the right direction?