From: Jeff King <peff@peff.net>
To: Erik Faye-Lund <kusmabite@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org, msysgit@googlegroups.com
Subject: Re: [PATCH/RFC 1/5] mingw: make fgetc raise SIGINT if apropriate
Date: Sat, 1 Dec 2012 12:39:43 -0500 [thread overview]
Message-ID: <20121201173943.GA18339@sigill.intra.peff.net> (raw)
In-Reply-To: <CABPQNSZaaZsfcC6dHDEhYUDpX4doQC7H=1VHGHuqfU4+m31jkA@mail.gmail.com>
On Sat, Dec 01, 2012 at 01:31:23PM +0100, Erik Faye-Lund wrote:
> >> One thing you might want to mention is that the fgetc() handling is not
> >> thread-safe, and intentionally so: if two threads read from the same
> >> console, we are in trouble anyway.
> >
> > That makes sense to me, but I'm confused why it is part of mingw_fgetc,
> > which could in theory read from arbitrary streams, no? It it is not
> > necessarily a console operation at all. I feel like I'm probably missing
> > something subtle here...
>
> I did add an early out for the non-console cases. Is this what you're
> missing, perhaps?
Oops, yes. That is exactly what I was missing. :)
Sorry for the noise.
-Peff
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
next prev parent reply other threads:[~2012-12-01 17:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 14:04 [PATCH/RFC 0/5] win32: support echo for terminal-prompt Erik Faye-Lund
2012-11-13 14:04 ` [PATCH/RFC 1/5] mingw: make fgetc raise SIGINT if apropriate Erik Faye-Lund
2012-11-30 17:58 ` Johannes Schindelin
2012-11-30 18:11 ` [msysGit] " Jeff King
2012-12-01 12:31 ` Erik Faye-Lund
2012-12-01 17:39 ` Jeff King [this message]
2012-12-01 12:36 ` Erik Faye-Lund
2012-12-04 17:12 ` Johannes Schindelin
2012-12-04 17:40 ` Erik Faye-Lund
2012-12-02 10:42 ` Junio C Hamano
2012-12-03 23:29 ` Erik Faye-Lund
2012-12-04 0:23 ` Junio C Hamano
2012-11-13 14:04 ` [PATCH/RFC 2/5] compat/terminal: factor out echo-disabling Erik Faye-Lund
2012-11-30 17:59 ` Johannes Schindelin
2012-11-30 18:19 ` Jeff King
2012-12-01 12:43 ` Erik Faye-Lund
2012-12-04 17:12 ` Johannes Schindelin
2012-11-13 14:04 ` [PATCH/RFC 3/5] compat/terminal: separate input and output handles Erik Faye-Lund
2012-11-30 18:22 ` Jeff King
2012-11-13 14:04 ` [PATCH/RFC 4/5] mingw: reuse tty-version of git_terminal_prompt Erik Faye-Lund
2012-11-30 18:05 ` Johannes Schindelin
2012-11-30 18:27 ` Jeff King
2012-11-13 14:04 ` [PATCH/RFC 5/5] mingw: get rid of getpass implementation Erik Faye-Lund
2012-11-30 18:06 ` Johannes Schindelin
2012-11-30 18:27 ` Jeff King
2012-11-30 10:16 ` [PATCH/RFC 0/5] win32: support echo for terminal-prompt Erik Faye-Lund
2012-11-30 18:30 ` Jeff King
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=20121201173943.GA18339@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
--cc=msysgit@googlegroups.com \
/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).