Google Git
Sign in
eclipse / linuxtools / org.eclipse.linuxtools / b9acdde66cb6a6385264bb9392410f46851880fa
commitb9acdde66cb6a6385264bb9392410f46851880fa[log] [tgz]
authorJeff Johnston <jjohnstn@redhat.com>Wed Aug 24 16:31:49 2016 -0400
committerJeff Johnston <jjohnstn@redhat.com>Thu Aug 25 17:43:04 2016 -0400
treef2b636b0a342c16d31587e9714cdec9c46f65d3c
parentc6acd9b9ec0b25f190c0030310ffb43e46e892c5 [diff]
Bug 499954 - Container with TTY doesn't display log or remove logs

- for terminals, always wait for container to be running or else
  finished

Change-Id: I26a46657bf635e318b1fa0a35275dd0b78ccfd8b
Reviewed-on: https://git.eclipse.org/r/79670
Tested-by: Hudson CI
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
1 file changed
tree: f2b636b0a342c16d31587e9714cdec9c46f65d3c
  1. changelog/
  2. containers/
  3. gcov/
  4. gprof/
  5. javadocs/
  6. libhover/
  7. lttng/
  8. man/
  9. oprofile/
  10. perf/
  11. profiling/
  12. releng/
  13. rpm/
  14. systemtap/
  15. vagrant/
  16. valgrind/
  17. .gitignore
  18. pom.xml
  19. README.md
README.md

Contributing to Linux Tools

Thanks for your interest in this project.

Project description:

The Linux Tools project aims to bring a full-featured C and C++ IDE to Linux developers. We build on the source editing and debugging features of the CDT and integrate popular native development tools such as the GNU Autotools, Valgrind, OProfile, RPM, SystemTap, GCov, GProf, LTTng, etc. Current projects include LTTng trace viewers and analyzers, an RPM .spec editor, Autotools build integration, a Valgrind heap usage analysis tool, and OProfile call profiling tools. The project also provides a place for Linux distributions to collaboratively overcome issues surrounding distribution packaging of Eclipse technology. The project produces both best practices and tools related to packaging. One of our features is a source archive of the Eclipse SDK that can be used by all Linux distributions building and distributing it.

Developer resources:

Information regarding source code management, builds, coding standards, and more.

Contributor License Agreement:

Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).

Contact:

Contact the project developers via the project's “dev” list.

Search for bugs:

This project uses Bugzilla to track ongoing development and issues.

Create a new bug:

Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!