From: Marat Radchenko <marat@slonopotamus.org>
To: git@vger.kernel.org
Subject: [BUG] git push writes to stderr instead of stdout on success
Date: Mon, 19 May 2014 19:03:58 +0400 [thread overview]
Message-ID: <20140519150358.GA3099@seldon> (raw)
`git push` writes to stderr instead of stdout
Steps to reproduce:
mkdir foo
cd foo
git init
echo foo > fo
git add -A
git commit -am "foo"
git push . HEAD:refs/heads/newbranch 2>out
Expected: `out` file is empty
Actual: `out` file contents:
To .
* [new branch] HEAD -> newbranch
next reply other threads:[~2014-05-19 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 15:03 Marat Radchenko [this message]
2014-05-19 15:49 ` [BUG] git push writes to stderr instead of stdout on success Jeff King
2014-05-19 16:43 ` Marat Radchenko
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=20140519150358.GA3099@seldon \
--to=marat@slonopotamus.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.