From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: StGIT cannot import properly from stdin
Date: Thu, 22 Sep 2005 17:06:40 +0200 [thread overview]
Message-ID: <4332C880.1060906@drzeus.cx> (raw)
In-Reply-To: <tnxr7bh188q.fsf@arm.com>
Catalin Marinas wrote:
>It looks like a problem with Python since it re-opens sys.stdin once
>it receives EOF.
>
>
>
Bummer. I checked with the local Python guru here and he suggested
changing the for loop to an infinite while and f.readline().
>I was referring to the 'cache the input to memory' variant, which is a
>bit more complicated. Caching to a file is simple but do you need to
>read patches from the terminal directly?
>
>
>
I don't explicitly need it, but it keeps things simple for me. I can
copy and paste the patch from my mailer without having to bother with
saving it to a temporary file.
next prev parent reply other threads:[~2005-09-22 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 7:12 StGIT cannot import properly from stdin Pierre Ossman
2005-09-21 8:03 ` Catalin Marinas
2005-09-22 11:08 ` Pierre Ossman
2005-09-22 12:11 ` Catalin Marinas
2005-09-22 14:05 ` Pierre Ossman
2005-09-22 14:34 ` Catalin Marinas
2005-09-22 15:06 ` Pierre Ossman [this message]
2005-09-22 15:42 ` Catalin Marinas
2005-09-22 15:48 ` Catalin Marinas
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=4332C880.1060906@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.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).