git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [BULLS**T PATCH] Allow Git to work at Insane Bank Corp
Date: Wed, 14 Nov 2007 19:36:11 -0800	[thread overview]
Message-ID: <7vlk9089jo.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20071115015227.GA2116@spearce.org> (Shawn O. Pearce's message of "Wed, 14 Nov 2007 20:52:27 -0500")

"Shawn O. Pearce" <spearce@spearce.org> writes:

> Because Insane Bank Corp is one of the largest banks in the world
> all 3rd party software vendors must comply and correct their
> applications to not fail when they encounter Desktop.ini in an
> application's internal data directory.  Or they will lose their
> contract with Insane Bank Corp.
>
> This patch must be applied to Git, since Git is a 3rd party software
> product and its global assets are much smaller than those of Insane
> Bank Corp.  If not applied Git won't be permitted for use.  Git could
> lose all of its software licenses and support contracts.  Git shall
> do as Insane Bank Corp requests.

.gitignore?	... ducks ... then comes back.

> +#ifdef WORK_FOR_INSANE_BANK_CORP
> +static inline struct dirent *gitreaddir(DIR *dirp)
> +{
> +	struct dirent *r;
> +	while ((r = readdir(dirp))) {
> +		if (!strcasecmp(r->d_name, "Desktop.ini"))
> +			continue;
> +	}
> +	return r;
> +}
> +#define readdir gitreaddir
> +#endif

Something like this could be used as an emulation layer for
case-corrupting filesystems ;-)

      parent reply	other threads:[~2007-11-15  3:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15  1:52 [BULLS**T PATCH] Allow Git to work at Insane Bank Corp Shawn O. Pearce
2007-11-15  2:13 ` Johannes Schindelin
2007-11-15  2:27   ` Shawn O. Pearce
2007-11-15  2:30 ` Morten Welinder
2007-11-15  3:36 ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vlk9089jo.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).