From: Larry D'Anna <larry@elder-gods.org>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH ld/maint-diff-quiet-w] Windows: redirect fopen("/dev/null") to fopen("nul")
Date: Thu, 25 Feb 2010 11:20:32 -0500 [thread overview]
Message-ID: <20100225162032.GA3527@cthulhu> (raw)
In-Reply-To: <4B86399E.3090508@viscovery.net>
* Johannes Sixt (j.sixt@viscovery.net) [100225 03:49]:
> From: Johannes Sixt <j6t@kdbg.org>
>
> An instance of fopen("/dev/null",...) was added to the code base. On
> Windows, we have to use "nul" instead. This implements a compatibility
> wrapper of fopen() that checks for this particular condition.
Doesn't store_updated_refs do this too?
--larry
next prev parent reply other threads:[~2010-02-25 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 8:49 [PATCH ld/maint-diff-quiet-w] Windows: redirect fopen("/dev/null") to fopen("nul") Johannes Sixt
2010-02-25 16:20 ` Larry D'Anna [this message]
2010-02-25 17:03 ` Junio C Hamano
2010-02-25 20:03 ` [PATCH maint] Windows: redirect f[re]open("/dev/null") to f[re]open("nul") Johannes Sixt
2010-02-25 20:16 ` [PATCH ld/maint-diff-quiet-w] Windows: redirect fopen("/dev/null") to fopen("nul") Junio C Hamano
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=20100225162032.GA3527@cthulhu \
--to=larry@elder-gods.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
/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).