Google Git
Sign in
eclipse / gerrit / linuxtools / org.eclipse.linuxtools / a979f2f3c21b5dc39191c5ab588f96d440e7b308
commita979f2f3c21b5dc39191c5ab588f96d440e7b308[log] [tgz]
authorJeff Johnston <jjohnstn@redhat.com>Mon Jun 09 16:32:32 2014 -0400
committerJeff Johnston <jjohnstn@redhat.com>Mon Jun 09 17:53:51 2014 -0400
tree4616197370097e86eb5387bd311832266abc6100
parent24b472170601315d9399e9797684fc5d6dc65d1b [diff]
Remove SNAPSHOT from parent versions but leave in for features/plugins.

- Also change all p2.inf to refer to update site instead of updates-nightly.

Change-Id: Ib867065a6d7d2f363cd3c33655f816b887254b22
Reviewed-on: https://git.eclipse.org/r/28234
Tested-by: Hudson CI
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
Tested-by: Jeff Johnston <jjohnstn@redhat.com>
245 files changed
tree: 4616197370097e86eb5387bd311832266abc6100
  1. changelog/
  2. gcov/
  3. gprof/
  4. libhover/
  5. lttng/
  6. man/
  7. oprofile/
  8. perf/
  9. profiling/
  10. releng/
  11. rpm/
  12. systemtap/
  13. valgrind/
  14. .gitignore
  15. pom.xml
  16. 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!