Sent: Wednesday, April 19, 2006 8:56 PM
> To: cygwin-patches@cygwin.com
> Cc: cygwin@cygwin.com
> Subject: [NON-WHINE] RE: mkstemp vs. text mode
>
> > From: Gary R. Van Sickle
> >
> > > From: Gary R. Van Sickle
> > >
> > > > From: Christopher
> From: Gary R. Van Sickle
>
> > From: Gary R. Van Sickle
> >
> > > From: Christopher Faylor
> > [snip]
> > > Yes, I think it makes sense to open temp files in binary
> > but I'll bet
> > > that someone is relying on textmode behavior.
> >
> > I'll see that bet and raise you; I'll bet this resul
> From: Gary R. Van Sickle
>
> > From: Christopher Faylor
> [snip]
> > Yes, I think it makes sense to open temp files in binary
> but I'll bet
> > that someone is relying on textmode behavior.
>
> I'll see that bet and raise you; I'll bet this results in
> massive problems.
>
> > Nevertheless
> From: Christopher Faylor
[snip]
> Yes, I think it makes sense to open temp files in binary but
> I'll bet that someone is relying on textmode behavior.
I'll see that bet and raise you; I'll bet this results in massive problems.
> Nevertheless, I've applied the patch.
>
> Let the cygwin ML w
On Mon, Apr 17, 2006 at 06:18:38AM -0600, Eric Blake wrote:
>Should we change mkstemp to always open in binary mode, regardless of
>the mount mode of the directory of the template name? Arguments for
>this is that mkstemp is often used by programs for binary data, where a
>text-mode /tmp mount poi
