From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Catalin Marinas <catalin.marinas@gmail.com>, git@vger.kernel.org
Subject: StGIT cannot import properly from stdin
Date: Wed, 21 Sep 2005 09:12:07 +0200 [thread overview]
Message-ID: <433107C7.60901@drzeus.cx> (raw)
The import command of stgit does not handle stdin in a very sane way.
The logic expects to be able to read the patch several times which isn't
possible with stdin. So for it to work you have to give it the patch twice.
A simple solution would be to store it to disk and then handle it the
same way as if a file had been given on the command line.
Rgds
Pierre
next reply other threads:[~2005-09-21 7:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 7:12 Pierre Ossman [this message]
2005-09-21 8:03 ` StGIT cannot import properly from stdin 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
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=433107C7.60901@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).