Comments for Andreas Jacobsen's Distraction

Comment on Subversion sucks, get over it by arealprogrammer

arealprogrammer — Fri, 16 Mar 2012 11:06:10 +0000

99% of code written is mundane uninspired hacks anyway, so really I think it’s programmers who have to get over themselves. It doesn’t matter where you store your code, it sucks, get over it. I think it’s a hoot that wars develop over a simple code repository, do you really think you matter all that much?

Comment on Subversion sucks, get over it by anonymous

anonymous — Wed, 07 Mar 2012 17:55:43 +0000

ur stupid

Comment on Where to find the NetBeans cheat sheet by Janio

Janio — Mon, 05 Mar 2012 16:45:24 +0000

I known most of the shortcuts for NetBeans, but I have never seen this card option in Help, great!

Comment on Subversion sucks, get over it by mabri

mabri — Sun, 17 Jul 2011 11:41:13 +0000

@Ben, comment #128: to solve what you call the “problem of real-time versioning” one would use a
versioning filesystem, not a version control system, IMHO. I for one like determine what goes together in a
changeset or revision, what the commit message reads, and don’t like my every file save to be versioned,
as it would be with inotify (at least not in the or a project’s repository).

Comment on Using Python setuptools on the mac by Install issue pymongo on OSX (setuptools out of date) | Rusty Razor Blade

Install issue pymongo on OSX (setuptools out of date) | Rusty Razor Blade — Fri, 22 Apr 2011 23:32:23 +0000

[...] issue where it uses a specific version of setuptools. You can read a really good explanation by Andreas Jacobsen [...]

Comment on Subversion sucks, get over it by Brian M

Brian M — Fri, 02 Jul 2010 06:05:30 +0000

Let’s see SVN do this:

Create a complete base tree of source. Create a sub project and Call it DEV.
Create another sub project off the root called QA. Now, SHARE all of the files from DEV into QA. Call a batch file that PINS everything.
Create a sub project off of the root called RELEASE. Share all the files from DEV in QA and call a batch file that PINS everything.

If I fix bugs, I do it in dev. I “promote” to QA by simply un-pinning the file in QA and re-pinning at the new version. My builds all run off of QA source.

When QA gives the green light, everything in RELEASE is unpinned and re-pinned at the QA version.

This is idiot-proof. I know, I have worked with so many idiots it’s hard to count. You SVN guys, I hope to hell you don’t make a mistake merging all of that spaghetti. Good Luck.

And, as if having to run a utility once a week to compact your database is such a big deal. Wusses.

Brian M.

Comment on ELisp best practices? by The Betacantrips Travelogue » Emacs Lisp Best Practices?

The Betacantrips Travelogue » Emacs Lisp Best Practices? — Sat, 24 Apr 2010 23:39:41 +0000

[...] one page wondering the same thing. There’s always a ton of interesting stuff whenever you go poking at emacs packages; most [...]

Comment on Subversion sucks, get over it by Andreas Krey

Andreas Krey — Tue, 17 Nov 2009 10:46:08 +0000

If it were only six minutes. I just made a wrong svn switch (forgot the last component in the path; trunk/c to branches/wawa instead of branches/wawa/c), Ctrl-C’ed it after I saw Makefile disappear. After that svn switch or update call for cleanup, and cleanup does not work. Thus I had to re-checkout everything — over GPRS. Real fun ensued. (The big subtree was already gone in the old sandbox, so rescuing it wouldn’t be any faster.)

Now if it were as easy to kill repositories…

Comment on Upgrading Ubuntu after EOL by Andreas

Andreas — Mon, 09 Nov 2009 07:49:05 +0000

A very useful resource indeed, thanks.

Comment on Upgrading Ubuntu after EOL by Wesley Schwengle

Wesley Schwengle — Sun, 08 Nov 2009 20:08:35 +0000

Hi, you might want to have a look here too: https://help.ubuntu.com/community/EOLUpgrades