Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

cmd/go: all output should go to either stdout or stderr #4917

Closed
adg opened this issue Feb 25, 2013 · 4 comments
Closed

cmd/go: all output should go to either stdout or stderr #4917

adg opened this issue Feb 25, 2013 · 4 comments
Labels
FrozenDueToAge
Milestone
Go1.1

Comments

@adg
Copy link
Contributor

adg commented Feb 25, 2013 

At the moment the output of some commands goes to stdout, and some goes to stderr. I
have suspicions that some commands write to both.

This should be made consistent.
@rsc
Copy link
Contributor

rsc commented Feb 25, 2013

Comment 1:

It can be made consistent in cmd/go instead of needing to change 6g etc.

@davecheney
Copy link
Contributor

Comment 2:

Link to discussion: https://groups.google.com/d/topic/golang-nuts/mravRwqB1CM/discussion

@gopherbot
Copy link

Comment 3 by jeff.allen:

This CL will fix this issue: https://golang.org/cl/7393073/

@adg
Copy link
Contributor Author

adg commented Mar 11, 2013

Comment 4:

This issue was closed by revision 53f034c.

Status changed to Fixed.

@adg adg added fixed labels Mar 11, 2013
@rsc rsc added this to the Go1.1 milestone Apr 14, 2015
@rsc rsc removed the go1.1maybe label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Go1.1
Development

No branches or pull requests
4 participants
@davecheney @rsc @adg @gopherbot