tag | 6f61d3e2ad9aaa7aa5658bedd58202acb9a7c1b4 | |
---|---|---|
tagger | Jeff Johnston <jjohnstn@redhat.com> | Tue Jun 07 17:54:43 2016 -0400 |
object | 4d86c7a081b74595b925ffa64c9578e36b0f7374 |
Linux Tools 5.0.0 release.
commit | 4d86c7a081b74595b925ffa64c9578e36b0f7374 | [log] [tgz] |
---|---|---|
author | Jeff Johnston <jjohnstn@redhat.com> | Tue Jun 07 13:34:55 2016 -0400 |
committer | Jeff Johnston <jjohnstn@redhat.com> | Tue Jun 07 16:22:06 2016 -0400 |
tree | 47548285f88bc6646716ad419d8f5e6a6f1d402d | |
parent | b0428db26fe44c375293762afe0725d85f4c270b [diff] |
Update Docker docs for Neon release. Change-Id: Ibc5f339eaad1c803179bf5e85bd56879d4d44bbf Reviewed-on: https://git.eclipse.org/r/74815 Tested-by: Hudson CI Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
Thanks for your interest in this project.
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.
Information regarding source code management, builds, coding standards, and more.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
Contact the project developers via the project's “dev” list.
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!