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.

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

Check if the stdout is a terminal in lxc-checkconfig #993

Merged
merged 1 commit into from
May 1, 2016

Conversation

walkerning
Copy link
Contributor

This makes me feel more convenient when reading a long lxc-checkconfig output using less or redirecting the lxc-checkconfig output to file for sending to others.

I don't know if you guys think this is necessary...

@lxc-jenkins
Copy link

This pull request didn't trigger Jenkins as its author isn't in the whitelist.

An organization member must perform one of the following:

  • To have this branch tested by Jenkins, use the "ok to test" command.
  • To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

@stgraber
Copy link
Member

stgraber commented May 1, 2016

That looks quite reasonable, however you need to sign-off your commit before we can accept it.

Please edit your commit message to include the required "Signed-off-by" line (see CONTRIBUTING).

Let lxc-checkconfig write to non-tty stdout without color control
characters
Signed-off-by: walkerning <foxdoraame@gmail.com>
@walkerning
Copy link
Contributor Author

@stgraber Sorry for not check the CONTRIBUTING docs before PR. Now I signed off my commits~

@stgraber stgraber merged commit 0aeed83 into lxc:master May 1, 2016
z-image pushed a commit to z-image/lxc that referenced this pull request Oct 16, 2016
Check if the stdout is a terminal in lxc-checkconfig
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants