Linux Tools 7.5.1 release
Changes for a 7.5.1 release

Change-Id: I7141aeb8d457b661b129305c9e568e4dae9a3b8d
Reviewed-on: https://git.eclipse.org/r/155884
Tested-by: Linux Tools Bot <linuxtools-bot@eclipse.org>
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
172 files changed
tree: 7606bcf85b559b95ed9e248dcb7f6798579c96e3
  1. .gitignore
  2. .project
  3. README.md
  4. changelog/
  5. containers/
  6. gcov/
  7. gprof/
  8. javadocs/
  9. libhover/
  10. lttng/
  11. man/
  12. oprofile/
  13. perf/
  14. pom.xml
  15. profiling/
  16. releng/
  17. rpm/
  18. systemtap/
  19. vagrant/
  20. valgrind/
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!