commit | f02bd5986c51b0a481fd6d775232a6ec9203c605 | [log] [tgz] |
---|---|---|
author | Roland Grunberg <rgrunber@redhat.com> | Mon Jun 27 10:53:32 2016 -0400 |
committer | Roland Grunberg <rgrunber@redhat.com> | Wed Jun 29 12:39:42 2016 -0400 |
tree | bfb65157917a86349502e0418431992f3725d2ef | |
parent | 3c0cc46126e275c2bb4e5e48f43ebd3654d84ac2 [diff] |
Bug 496784: Enable mass stop/kill of containers regardless of state. If a user wishes to stop/kill a large amount of containers (eg. by selecting all containers, the operation will become disabled since all selected containers must be in the running state. Relax this requirement and permit silent failure when trying to kill a stopped container. Change-Id: I59858fe05e7db038755cc736686d4c512914e0b3 Reviewed-on: https://git.eclipse.org/r/76017 Tested-by: Hudson CI Reviewed-by: Roland Grunberg <rgrunber@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!