Re: [BULLS**T PATCH] Allow Git to work at Insane Bank Corp

From: Shawn O. Pearce <spearce@spearce.org>
Date: Nov 15, 2007, 02:27 UTC
Message-ID: <20071115022759.GJ14735@spearce.org>
In-Reply-To: <Pine.LNX.4.64.0711150211360.4362@racer.site>

Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 8 quoted lines

> On Wed, 14 Nov 2007, Shawn O. Pearce wrote:
> 
> > For corporate security reasons it is obviously absolutely vital that
> > these Desktop.ini files exist in every directory of every system.
> 
> But seriously, some things like these should make it possible for one of 
> the fastest SCMs in the world (both in performance and in development) to 
> get some serious contracts.

Well, see, you can't actually use Git at Insane Bank Corp because it wasn't put on the approved list of software. Furthermore if it was put on that list it would probably only ever be approved for use on RedHat Linux, as on Windows there is Microsoft Visual Source Suck and on Solaris there is Rational ConfusingCase. All provide the same function and therefore are exactly suitable for those platforms.

Any deviants get Desktop.ini files where they don't want them.

Keep in mind that Insane Bank Corp has approved the following OS and database combinations, as they are all the same thing. Any mixing/matching is not permitted:

  OS         Database
  ------------------------------
  Windows    Microsoft SQL Server
  Solaris    Oracle
  AIX        IBM DB2
  Linux      MySQL

Because you can do anything that Oracle does with MySQL if Linux
is your OS.  Didn't you know that MySQL understands all of Oracle's
extended SQL syntax?  Silly developers.  :-)

> I mean, how does svn cope with something like that?

SVN probably doesn't care. As in SVN probably only scans the working directory, which you can tell it to ignore Desktop.ini files in. When it looks at the SVN/ metadata directory in a checkout it probably knows exactly what files its going after. Extra files don't matter to it.

In the fsfs and bdb backends SVN is probably again only going after known filenames. So it probably isn't impacted by extra crap shoved into the directory.

I'm waiting for the next release of the desktop security software, the one that adds an extra 1M binary header to the front of every one of Java source files, because that's the only way they can protect the data that never should have been on a portable computing device in the first place.

I can't wait for Java 6 update 4 Special Edition for Insane Bank Corp version to be rolled out to ignore those headers. Or for the Eclipse 3.3.1.1.1 release which will also ignore those headers.

-- 
Shawn.