Google Git
Sign in
eclipse / linuxtools / org.eclipse.linuxtools / f75f3f6903de3b81373f69c800539f222a0a4e54
commitf75f3f6903de3b81373f69c800539f222a0a4e54[log] [tgz]
authorJeff Johnston <jjohnstn@redhat.com>Tue Sep 15 16:11:31 2015 -0400
committerJeff Johnston <jjohnstn@redhat.com>Tue Sep 15 19:11:46 2015 -0400
treedf2942dd166871afcc52283d520b3e8c9296e56c
parente277da29e4338852fed77e31005e732c16b3a03b [diff]
Final changes for 4.1.0 release

- change all update sites in p2.inf files to be either update or
  update-docker
- remove SNAPSHOT from all parent and groupids but leave for
  features/plug-ins
- fix 4.5 target to use CDT milestones repo which has 8.8 now

Change-Id: Ib8a794c0ad2f42b82d684a4766aa5f855d82db88
Reviewed-on: https://git.eclipse.org/r/56028
Tested-by: Hudson CI
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
164 files changed
tree: df2942dd166871afcc52283d520b3e8c9296e56c
  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. valgrind/
  16. .gitignore
  17. pom.xml
  18. 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!