Journal FortKnox's Journal: Source Control System 17
I have an idea for a new source control system. Attach a FPS, and for all conflicts, you must duke it out to determine if your code gets overwritten, or you do the writing.
A duel to the death? No! To the pain! First you will lose your fingers, then your hands at the wrist, then come your toes followed by your feet...
A duel to the death? No! To the pain! First you will lose your fingers, then your hands at the wrist, then come your toes followed by your feet...
Good for the young guys (Score:2)
Now if you had to write code to fight your opponent's code- and the strongest code won....
What am I talking about? I work in an office with 2 programmers and no version control. Never mind.
Re:Good for the young guys (Score:1)
Hello, my name is Inigo Montoya. (Score:4, Funny)
Inconceivable (Score:4, Funny)
Re:Hello, my name is Inigo Montoya. (Score:2)
I wish I could re-friend you, that was so great.
Re:Hello, my name is Inigo Montoya. (Score:2)
Re:Hello, my name is Inigo Montoya. (Score:2)
A Response that Bucks the Trend... (Score:2)
Aside: No. I have never had to use that line while I've had CVS-write access to the Slash codebase. Honestly!
good luck (Score:2)
think it'll work?
it'd take a miracle
ObLink (Score:2)
Never code a system... (Score:1)
Ha ha ha ha ha ha
Code Switching (Score:4, Funny)
Re:Code Switching (Score:2)
Re:Code Switching (Score:3, Funny)
(they were both patched, i've spent the last five years building up an immunity to software bugs.)
Re:Code Switching (Score:2)
Re:Code Switching (Score:4, Insightful)
Re:Code Switching (Score:1)
If there are, we all be dead!
No more changes now, I mean it!
Anybody want a peanut?