From: Ilija Pecelj <pecelj@gmail.com>
To: git@vger.kernel.org
Subject: Bug/comment
Date: Tue, 30 Jan 2018 00:21:44 +0100 [thread overview]
Message-ID: <2df7b921-6fe2-d55f-4ef0-3f4f0bd69261@gmail.com> (raw)
Though it might not be considered a bug 'per se' it is definitely wired.
Namely, when you type 'yes' word and hit enter in git bash for widnows,
the process enters infinite loop and just prints 'y' letter in new line.
It can be interrupted with CTRL+C. I'm not sure if it has any other
consequences other than printing letter 'y' in infinite loop.
Cheers,
Ilija
next reply other threads:[~2018-01-29 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 23:21 Ilija Pecelj [this message]
2018-01-30 0:02 ` Bug/comment Andrew Ardill
2018-01-31 17:38 ` Bug/comment Kaartic Sivaraam
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=2df7b921-6fe2-d55f-4ef0-3f4f0bd69261@gmail.com \
--to=pecelj@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).