[GEANT-102] This is the catch-all Jira issue for small fixes Created: 16/May/14  Updated: 28/Nov/17

Status: In Progress
Project: Geant detector simulation prototype
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Federico Carminati Assignee: Pere Mato Vila
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Planned Start:
Planned End:
Component Watchers:

 Description   

We use this issue as a catch-all for very small corrections



 Comments   
Comment by Federico Carminati [ 16/May/14 ]

From now on please commit all small fixes with the prefix GEANT-102 in the message, so that they are linked to this catch-all Jira issue.

Comment by GitLab service [ 05/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 05/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 05/Nov/15 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 05/Nov/15 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant.

Comment by Sandro Christian Wenzel [ 05/Nov/15 ]

Oksana Shadura mentioned this issue in a commit of VecGeom/VecGeom.

Comment by Sandro Christian Wenzel [ 05/Nov/15 ]

Oksana Shadura mentioned this issue in a merge request of VecGeom/VecGeom.

Comment by GitLab service [ 05/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 05/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 05/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 05/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 05/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 06/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by Sandro Christian Wenzel [ 09/Nov/15 ]

Oksana Shadura mentioned this issue in a commit of VecGeom/VecGeom.

Comment by GitLab service [ 18/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 18/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 18/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 19/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 19/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 19/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 19/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 19/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 19/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 19/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 20/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 20/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 20/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 20/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 20/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 20/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 20/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 20/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 20/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 20/Nov/15 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 08/Dec/15 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 19/Jan/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 19/Jan/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 19/Jan/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 19/Jan/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 19/Jan/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 19/Jan/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 19/Jan/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 10/Feb/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 10/Feb/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 10/Feb/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 10/Feb/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 10/Feb/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 10/Feb/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 10/Feb/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 08/Mar/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 08/Mar/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 08/Mar/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 08/Mar/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 08/Mar/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 08/Mar/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 08/Mar/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 16/Mar/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 16/Mar/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 16/Mar/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 16/Mar/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 16/Mar/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 16/Mar/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 16/Mar/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 08/Apr/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 08/Apr/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 08/Apr/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 08/Apr/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 08/Apr/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 08/Apr/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 08/Apr/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 12/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 12/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 12/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 12/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 13/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 13/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 13/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 13/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 13/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 13/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 20/May/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 23/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 23/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 23/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 24/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 24/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 25/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 25/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 25/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 25/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 25/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 25/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 25/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 25/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 25/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 25/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 25/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 25/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 25/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 26/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 27/May/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant.

Comment by GitLab service [ 03/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Suppress unused parameter warning'

Comment by GitLab service [ 03/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Since Smearer has no virtual function use ClassDefNV'

Comment by GitLab service [ 03/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Comment out unused variable'

Comment by GitLab service [ 03/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Avoid unused variable warning'

Comment by GitLab service [ 03/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 White space'

Comment by GitLab service [ 03/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Resolve warning about undeclared friend'

Comment by GitLab service [ 03/Jun/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Adding VECCORE project support for JIRA naming hook'

Comment by GitLab service [ 03/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Master compiles again without warnings'

Comment by GitLab service [ 03/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Master compiles again without warnings'

Comment by GitLab service [ 03/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Master compiles again without warnings'

Comment by GitLab service [ 03/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fixing last remaining warnings'

Comment by GitLab service [ 03/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 clang-format'

Comment by GitLab service [ 03/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fix latest merge from Soon'

Comment by GitLab service [ 03/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'Revert "GEANT-102 fix latest merge from Soon"'

Comment by GitLab service [ 03/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Commenting unused paramaters and using proper types instead of auto to make Vc happy'

Comment by GitLab service [ 03/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 add -fabi-version=6 for gcc 4.x'

Comment by GitLab service [ 03/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix typo and add if on use(ish) of Vc'

Comment by GitLab service [ 03/Jun/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix tiny typo - errors in CDASH'

Comment by GitLab service [ 03/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Options should not be added as strings'

Comment by GitLab service [ 03/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Options should not be added as strings'

Comment by GitLab service [ 03/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Removing unused z0 variable'

Comment by GitLab service [ 03/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Clang formatting'

Comment by GitLab service [ 03/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Removing unused dz0 variable'

Comment by GitLab service [ 03/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Removing unused PositionMomentum variable'

Comment by GitLab service [ 03/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Clang Format'

Comment by GitLab service [ 03/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Clang Format'

Comment by GitLab service [ 03/Jun/16 ]

Witold Pokorski mentioned this issue in a commit of GeantV/geant:
'GEANT-102 resolve conflict - use one in the HEAD'

Comment by GitLab service [ 03/Jun/16 ]

Witold Pokorski mentioned this issue in a commit of GeantV/geant:
'GEANT-102 resolve conflict - use one in the HEAD'

Comment by GitLab service [ 03/Jun/16 ]

Witold Pokorski mentioned this issue in a commit of GeantV/geant:
'GEANT-102 resolve conflict - use one in the HEAD'

Comment by GitLab service [ 03/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 clang-format'

Comment by GitLab service [ 03/Jun/16 ]

Witold Pokorski mentioned this issue in a commit of GeantV/geant:
'GEANT-102 resolve conflict one more time - use one in the HEAD'

Comment by GitLab service [ 03/Jun/16 ]

Witold Pokorski mentioned this issue in a commit of GeantV/geant:
'GEANT-102 revert the use of auto to int due to compilation error from Vc: version dependent?'

Comment by GitLab service [ 03/Jun/16 ]

Witold Pokorski mentioned this issue in a commit of GeantV/geant:
'GEANT-102 remove warnings for unused variables - we need a method to add an in¿'

Comment by GitLab service [ 03/Jun/16 ]

Witold Pokorski mentioned this issue in a commit of GeantV/geant:
'GEANT-102 remove warnings for unused parameter'

Comment by GitLab service [ 03/Jun/16 ]

Witold Pokorski mentioned this issue in a commit of GeantV/geant:
'GEANT-102 removing unnecessary options and variables taken from fca/vecphys'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 sincos is provided by NVCC'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Enable ROOT dictionary generation'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix warning about format'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Removing redundand includes'

Comment by GitLab service [ 06/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix typo and add if on use(ish) of Vc'

Comment by GitLab service [ 06/Jun/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix tiny typo - errors in CDASH'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Options should not be added as strings'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Options should not be added as strings'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Removing unused z0 variable'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Clang formatting'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Removing unused dz0 variable'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Removing unused PositionMomentum variable'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Clang Format'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Clang Format'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 resolve conflict - use one in the HEAD'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 resolve conflict - use one in the HEAD'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 resolve conflict - use one in the HEAD'

Comment by GitLab service [ 06/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 clang-format'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 resolve conflict one more time - use one in the HEAD'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 revert the use of auto to int due to compilation error from Vc: version dependent?'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 remove warnings for unused variables - we need a method to add an in¿'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 remove warnings for unused parameter'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 sincos is provided by NVCC'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Enable ROOT dictionary generation'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix warning about format'

Comment by GitLab service [ 06/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Removing redundand includes'

Comment by GitLab service [ 07/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Suppress unused parameter warning'

Comment by GitLab service [ 07/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Since Smearer has no virtual function use ClassDefNV'

Comment by GitLab service [ 07/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Comment out unused variable'

Comment by GitLab service [ 07/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Avoid unused variable warning'

Comment by GitLab service [ 07/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 White space'

Comment by GitLab service [ 07/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Resolve warning about undeclared friend'

Comment by GitLab service [ 07/Jun/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Adding VECCORE project support for JIRA naming hook'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Master compiles again without warnings'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Master compiles again without warnings'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Master compiles again without warnings'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fixing last remaining warnings'

Comment by GitLab service [ 07/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 clang-format'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fix latest merge from Soon'

Comment by GitLab service [ 07/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'Revert "GEANT-102 fix latest merge from Soon"'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Commenting unused paramaters and using proper types instead of auto to make Vc happy'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 add -fabi-version=6 for gcc 4.x'

Comment by GitLab service [ 07/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix typo and add if on use(ish) of Vc'

Comment by GitLab service [ 07/Jun/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix tiny typo - errors in CDASH'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Options should not be added as strings'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Options should not be added as strings'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Removing unused z0 variable'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Clang formatting'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Removing unused dz0 variable'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Removing unused PositionMomentum variable'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Clang Format'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Clang Format'

Comment by GitLab service [ 07/Jun/16 ]

Andrei Gheata mentioned this issue in a commit of GeantV/geant:
'GEANT-102 resolve conflict - use one in the HEAD'

Comment by GitLab service [ 07/Jun/16 ]

Andrei Gheata mentioned this issue in a commit of GeantV/geant:
'GEANT-102 resolve conflict - use one in the HEAD'

Comment by GitLab service [ 07/Jun/16 ]

Andrei Gheata mentioned this issue in a commit of GeantV/geant:
'GEANT-102 resolve conflict - use one in the HEAD'

Comment by GitLab service [ 07/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 clang-format'

Comment by GitLab service [ 07/Jun/16 ]

Andrei Gheata mentioned this issue in a commit of GeantV/geant:
'GEANT-102 resolve conflict one more time - use one in the HEAD'

Comment by GitLab service [ 07/Jun/16 ]

Andrei Gheata mentioned this issue in a commit of GeantV/geant:
'GEANT-102 revert the use of auto to int due to compilation error from Vc: version dependent?'

Comment by GitLab service [ 07/Jun/16 ]

Andrei Gheata mentioned this issue in a commit of GeantV/geant:
'GEANT-102 remove warnings for unused variables - we need a method to add an in¿'

Comment by GitLab service [ 07/Jun/16 ]

Andrei Gheata mentioned this issue in a commit of GeantV/geant:
'GEANT-102 remove warnings for unused parameter'

Comment by GitLab service [ 07/Jun/16 ]

Andrei Gheata mentioned this issue in a commit of GeantV/geant:
'GEANT-102 removing unnecessary options and variables taken from fca/vecphys'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 removing annoying warning message about unused functions'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 avoid duplicate flags in case of build within GeantV'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 streamline includes'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use consistently .so on Mac'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a merge request of GeantV/geant:
'GEANT-102 Use consistently .so on Mac'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use consistently .so on Mac in installation'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 improve installation location of vecphys files'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 add possibility to delete installed files'

Comment by GitLab service [ 07/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use symbolic shared lib suffix'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 removing annoying warning message about unused functions'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 avoid duplicate flags in case of build within GeantV'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 streamline includes'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use consistently .so on Mac'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use consistently .so on Mac in installation'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 improve installation location of vecphys files'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 vecphys not a project per se'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fixing annoying warning on MAC OS X'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fixing macro who had stopped working'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 avoid -Weffc++ with gcc <= 4.8'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Schema Evolution'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fixing particle charge when not using ParticlePDG'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix versiondump on ubuntu'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fixing charge conventions'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Improving merge'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 GEANT_NVCC alerady defined in Config.h'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Fix format'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Fix format'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Fix format'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fixing macro who had stopped working'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Schema Evolution'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fixing particle charge when not using ParticlePDG'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix versiondump on ubuntu'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fixing charge conventions'

Comment by GitLab service [ 08/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 basic alternative implementation of error message handler'

Comment by GitLab service [ 08/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix compiler warnings'

Comment by GitLab service [ 08/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Remove unnecessary macro use'

Comment by GitLab service [ 08/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use delete to remove default function we don't want'

Comment by GitLab service [ 08/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 White spaces'

Comment by GitLab service [ 08/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Config.h must be the first include'

Comment by GitLab service [ 08/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use Geant's message logger'

Comment by GitLab service [ 08/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Suppress warning'

Comment by GitLab service [ 08/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix compiler warnings'

Comment by GitLab service [ 08/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 White space'

Comment by GitLab service [ 08/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Improving merge'

Comment by GitLab service [ 09/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Remove use of (unused per se) ClassImp macro.'

Comment by GitLab service [ 10/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 (kTRUE,kFALSE) -> (true, false)'

Comment by GitLab service [ 10/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 (kTRUE,kFALSE) -> (true, false)'

Comment by GitLab service [ 10/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fixes after merge'

Comment by GitLab service [ 13/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fixing macro who had stopped working'

Comment by GitLab service [ 13/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Schema Evolution'

Comment by GitLab service [ 13/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fixing particle charge when not using ParticlePDG'

Comment by GitLab service [ 13/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix versiondump on ubuntu'

Comment by GitLab service [ 13/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 basic alternative implementation of error message handler'

Comment by GitLab service [ 13/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix compiler warnings'

Comment by GitLab service [ 13/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use delete to remove default function we don't want'

Comment by GitLab service [ 13/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 White spaces'

Comment by GitLab service [ 13/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Config.h must be the first include'

Comment by GitLab service [ 13/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use Geant's message logger'

Comment by GitLab service [ 13/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Suppress warning'

Comment by GitLab service [ 13/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix compiler warnings'

Comment by GitLab service [ 13/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 White space'

Comment by GitLab service [ 13/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Reduce nesting of if'

Comment by GitLab service [ 14/Jun/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Adding missing libraries'

Comment by GitLab service [ 15/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 remove pragma message'

Comment by GitLab service [ 15/Jun/16 ]

Federico Carminati mentioned this issue in a merge request of GeantV/geant:
'GEANT-102 remove pragma message'

Comment by GitLab service [ 15/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 remove pragma message'

Comment by GitLab service [ 20/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 basic alternative implementation of error message handler'

Comment by GitLab service [ 20/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Add Geant::Printf, extend non-ROOT printing'

Comment by GitLab service [ 20/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fixing macro who had stopped working'

Comment by GitLab service [ 20/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Schema Evolution'

Comment by GitLab service [ 20/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fixing particle charge when not using ParticlePDG'

Comment by GitLab service [ 20/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix versiondump on ubuntu'

Comment by GitLab service [ 20/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix compiler warnings'

Comment by GitLab service [ 20/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use delete to remove default function we don't want'

Comment by GitLab service [ 20/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Config.h must be the first include'

Comment by GitLab service [ 20/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use Geant's message logger'

Comment by GitLab service [ 20/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Suppress warning'

Comment by GitLab service [ 20/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix compiler warnings'

Comment by GitLab service [ 20/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 White space'

Comment by GitLab service [ 20/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Reduce nesting of if'

Comment by GitLab service [ 20/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Remove unnecessary #ifdef'

Comment by GitLab service [ 20/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use std mutex/condition variable'

Comment by GitLab service [ 20/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix LaTex'

Comment by GitLab service [ 20/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Add all files to doxygen generation'

Comment by GitLab service [ 20/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Add all files to doxygen generation'

Comment by GitLab service [ 20/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Remove spurious Doxygen'

Comment by GitLab service [ 20/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Add missing header'

Comment by GitLab service [ 21/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Add all files to doxygen generation'

Comment by GitLab service [ 21/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Add missing header'

Comment by GitLab service [ 22/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Add missing header'

Comment by GitLab service [ 22/Jun/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Synchro of script comparing to VecGeom repo'

Comment by GitLab service [ 22/Jun/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Syncro of CI scripts is finished'

Comment by GitLab service [ 22/Jun/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 typo with endif() in CTest script'

Comment by GitLab service [ 22/Jun/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fixing typo'

Comment by GitLab service [ 22/Jun/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 One more typo'

Comment by GitLab service [ 22/Jun/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Typo in order of passing arguments'

Comment by GitLab service [ 23/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 basic alternative implementation of error message handler'

Comment by GitLab service [ 23/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Add Geant::Printf, extend non-ROOT printing'

Comment by GitLab service [ 23/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fixing macro who had stopped working'

Comment by GitLab service [ 23/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Schema Evolution'

Comment by GitLab service [ 23/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fixing particle charge when not using ParticlePDG'

Comment by GitLab service [ 23/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix versiondump on ubuntu'

Comment by GitLab service [ 23/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix compiler warnings'

Comment by GitLab service [ 23/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use delete to remove default function we don't want'

Comment by GitLab service [ 23/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Config.h must be the first include'

Comment by GitLab service [ 23/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use Geant's message logger'

Comment by GitLab service [ 23/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Suppress warning'

Comment by GitLab service [ 23/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix compiler warnings'

Comment by GitLab service [ 23/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 White space'

Comment by GitLab service [ 23/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Reduce nesting of if'

Comment by GitLab service [ 23/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Remove unnecessary #ifdef'

Comment by GitLab service [ 23/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use std mutex/condition variable'

Comment by GitLab service [ 23/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Removed unnecessary header'

Comment by GitLab service [ 28/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 basic alternative implementation of error message handler'

Comment by GitLab service [ 28/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Add Geant::Printf, extend non-ROOT printing'

Comment by GitLab service [ 28/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fixing macro who had stopped working'

Comment by GitLab service [ 28/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Schema Evolution'

Comment by GitLab service [ 28/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fixing particle charge when not using ParticlePDG'

Comment by GitLab service [ 28/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix versiondump on ubuntu'

Comment by GitLab service [ 28/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix compiler warnings'

Comment by GitLab service [ 28/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use delete to remove default function we don't want'

Comment by GitLab service [ 28/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Config.h must be the first include'

Comment by GitLab service [ 28/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use Geant's message logger'

Comment by GitLab service [ 28/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Suppress warning'

Comment by GitLab service [ 28/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix compiler warnings'

Comment by GitLab service [ 28/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 White space'

Comment by GitLab service [ 28/Jun/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Reduce nesting of if'

Comment by GitLab service [ 28/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Remove unnecessary #ifdef'

Comment by GitLab service [ 28/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Use std mutex/condition variable'

Comment by GitLab service [ 28/Jun/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Removed unnecessary header'

Comment by GitLab service [ 01/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Use Clang and AppleClang'

Comment by GitLab service [ 01/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Improve debug message'

Comment by GitLab service [ 01/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Add libraries for unresolved referecens'

Comment by GitLab service [ 01/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Mods from S.Vallecorsa to fix testserialReadCuda'

Comment by GitLab service [ 01/Jul/16 ]

Federico Carminati mentioned this issue in a merge request of GeantV/geant:
'GEANT-102Mods from S.Vallecorsa to fix testserialReadCuda'

Comment by GitLab service [ 01/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Mods from S.Vallecorsa to fix testserialReadCuda'

Comment by GitLab service [ 01/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Improve debug message'

Comment by GitLab service [ 01/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Add libraries for unresolved referecens'

Comment by GitLab service [ 01/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Remove debug message'

Comment by GitLab service [ 01/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Reduce dependencies (P.Canal)'

Comment by GitLab service [ 01/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102More cleanup (P.Canal)'

Comment by GitLab service [ 01/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Mods from S.Vallecorsa to fix testserialReadCuda'

Comment by GitLab service [ 01/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Use library target name and not file name'

Comment by GitLab service [ 01/Jul/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 warning: comparison between signed and unsigned integer expressions'

Comment by GitLab service [ 02/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Massive simplification of CMakeFiles.txt'

Comment by GitLab service [ 02/Jul/16 ]

Federico Carminati mentioned this issue in a merge request of GeantV/geant:
'WIP: GEANT-102Massive simplification of CMakeFiles.txt'

Comment by GitLab service [ 02/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Massive simplification of CMakeFiles.txt'

Comment by GitLab service [ 02/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Use library target name and not file name'

Comment by GitLab service [ 02/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Massive simplification of CMakeFiles.txt'

Comment by GitLab service [ 02/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Simplify also the test-LHCb CMakeFiles.txt'

Comment by GitLab service [ 05/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102CURRENT_CMAKE_SOURCE_DIR does not need to be specified'

Comment by GitLab service [ 05/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Massive simplification of CMakeFiles.txt'

Comment by GitLab service [ 05/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Simplify also the test-LHCb CMakeFiles.txt'

Comment by GitLab service [ 05/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102CURRENT_CMAKE_SOURCE_DIR does not need to be specified'

Comment by GitLab service [ 05/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Use library target name and not file name'

Comment by Geant Build Server [ 07/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Massive simplification of CMakeFiles.txt'

Comment by Geant Build Server [ 07/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Simplify also the test-LHCb CMakeFiles.txt'

Comment by Geant Build Server [ 07/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102CURRENT_CMAKE_SOURCE_DIR does not need to be specified'

Comment by Geant Build Server [ 07/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Use library target name and not file name'

Comment by Geant Build Server [ 10/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Use library target name and not file name'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Massive simplification of CMakeFiles.txt'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Simplify also the test-LHCb CMakeFiles.txt'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102CURRENT_CMAKE_SOURCE_DIR does not need to be specified'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Use library target name and not file name'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Massive simplification of CMakeFiles.txt'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Simplify also the test-LHCb CMakeFiles.txt'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102CURRENT_CMAKE_SOURCE_DIR does not need to be specified'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Massive simplification of CMakeFiles.txt'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Simplify also the test-LHCb CMakeFiles.txt'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102CURRENT_CMAKE_SOURCE_DIR does not need to be specified'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Use library target name and not file name'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Massive simplification of CMakeFiles.txt'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Simplify also the test-LHCb CMakeFiles.txt'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102CURRENT_CMAKE_SOURCE_DIR does not need to be specified'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Restore diagnostic print'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Do not use GENERATE_DICTIONARY when ROOT is Off'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Restore diagnostic print'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Remove ClassDef altogether for class that does not derinve from TObject'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Use add_compile_option'

Comment by Geant Build Server [ 13/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Further simplification of the code'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Remove useless ClassDef'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Massive simplification of CMakeFiles.txt'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Simplify also the test-LHCb CMakeFiles.txt'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102CURRENT_CMAKE_SOURCE_DIR does not need to be specified'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Use library target name and not file name'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Massive simplification of CMakeFiles.txt'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Simplify also the test-LHCb CMakeFiles.txt'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102CURRENT_CMAKE_SOURCE_DIR does not need to be specified'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Do not use GENERATE_DICTIONARY when ROOT is Off'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Restore diagnostic print'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Remove ClassDef altogether for class that does not derinve from TObject'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Use add_compile_option'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Further simplification of the code'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Remove useless ClassDef'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102CMake formatting'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Do not use TString and reduce code duplication'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Fixing a syntax error'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Reverting'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Saving modified option in the cache'

Comment by Geant Build Server [ 14/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Saving modified option in the cache'

Comment by Geant Build Server [ 15/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Put back stdarg.h so the source is self-consistent'

Comment by Geant Build Server [ 18/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Move TString to std::string where it makes sense'

Comment by Geant Build Server [ 18/Jul/16 ]

Federico Carminati mentioned this issue in a merge request of GeantV/geant:
'GEANT-102Move TString to std::string where it makes sense'

Comment by Geant Build Server [ 18/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Move TString to std::string where it makes sense'

Comment by Geant Build Server [ 18/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Move TString to std::string where it makes sense'

Comment by Geant Build Server [ 18/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102use long long int to guarantee 64 bits'

Comment by Geant Build Server [ 18/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102use long long int to guarantee 64 bits'

Comment by Geant Build Server [ 18/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Move using into implementation file'

Comment by Geant Build Server [ 18/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Move TString to std::string where it makes sense'

Comment by Geant Build Server [ 18/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102use long long int to guarantee 64 bits'

Comment by Geant Build Server [ 18/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102use long long int to guarantee 64 bits'

Comment by Geant Build Server [ 18/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Move using into implementation file'

Comment by Geant Build Server [ 18/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102put back string in case VECGEOM_NAVIGATOR is not used'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Break up CreateParticle to speed up compilation'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Restore CUDA compilation'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Break up CreateParticle to speed up compilation'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Restore CUDA compilation'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Remove old CreateParticle'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix generation of CUDA code'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Fixing some problems with CUDA'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Move TString to std::string where it makes sense'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102use long long int to guarantee 64 bits'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102use long long int to guarantee 64 bits'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Move using into implementation file'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102put back string in case VECGEOM_NAVIGATOR is not used'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Use GEANT flag for device'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 removing unused file'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 removing unused file'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Restore CUDA compilation'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Remove old CreateParticle'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix generation of CUDA code'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fixing some problems with CUDA'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Restore CUDA compilation'

Comment by Geant Build Server [ 19/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Fixing some problems with CUDA'

Comment by Geant Build Server [ 20/Jul/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Move generated files into their own directory'

Comment by Geant Build Server [ 20/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Move TString to std::string where it makes sense'

Comment by Geant Build Server [ 20/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102use long long int to guarantee 64 bits'

Comment by Geant Build Server [ 20/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102use long long int to guarantee 64 bits'

Comment by Geant Build Server [ 20/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Move using into implementation file'

Comment by Geant Build Server [ 20/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102put back string in case VECGEOM_NAVIGATOR is not used'

Comment by Geant Build Server [ 20/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Move TString to std::string where it makes sense'

Comment by Geant Build Server [ 20/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102use long long int to guarantee 64 bits'

Comment by Geant Build Server [ 20/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102use long long int to guarantee 64 bits'

Comment by Geant Build Server [ 20/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Move using into implementation file'

Comment by Geant Build Server [ 20/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102put back string in case VECGEOM_NAVIGATOR is not used'

Comment by Geant Build Server [ 27/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Fixing small bug'

Comment by Geant Build Server [ 28/Jul/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Fix include for incomplete type'

Comment by Geant Build Server [ 04/Aug/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Fix bug'

Comment by Geant Build Server [ 04/Aug/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Fix bug'

Comment by Geant Build Server [ 04/Aug/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Fix bug'

Comment by Geant Build Server [ 04/Aug/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Remove in favor of VecGeom version'

Comment by Geant Build Server [ 04/Aug/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Bug Fix'

Comment by Geant Build Server [ 04/Aug/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Remove useless includes'

Comment by Geant Build Server [ 04/Aug/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Removing annoying pragma message'

Comment by Geant Build Server [ 04/Aug/16 ]

Federico Carminati mentioned this issue in a commit of GeantV/geant:
'GEANT-102Removing annoying pragma message'

Comment by Geant Build Server [ 29/Aug/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fix a compilation error from KNC'

Comment by Geant Build Server [ 29/Aug/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fix for edge problems in sampling secondaries'

Comment by Geant Build Server [ 29/Aug/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fix for edge problems in sampling secondaries'

Comment by Geant Build Server [ 29/Aug/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 29/Aug/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 29/Aug/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 29/Aug/16 ]

Soon Yung Jun mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 30/Aug/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Adding one more CI node label without broken nodes'

Comment by Geant Build Server [ 30/Aug/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Compiler settings for CI label without broken nodes'

Comment by Geant Build Server [ 01/Sep/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Adding one more CI node label without broken nodes'

Comment by Geant Build Server [ 01/Sep/16 ]

Oksana Shadura mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Compiler settings for CI label without broken nodes'

Comment by Geant Build Server [ 12/Sep/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Readd defaulting of BACKEND.'

Comment by Geant Build Server [ 12/Sep/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Readd defaulting of BACKEND.'

Comment by Geant Build Server [ 12/Sep/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix spelling of ACos to match VecCore's.'

Comment by Geant Build Server [ 12/Sep/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Fix spelling of ACos to match VecCore's.'

Comment by Geant Build Server [ 20/Sep/16 ]

Harphool Kumawat mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fix a compilation error from KNC'

Comment by Geant Build Server [ 20/Sep/16 ]

Harphool Kumawat mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fix for edge problems in sampling secondaries'

Comment by Geant Build Server [ 20/Sep/16 ]

Harphool Kumawat mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fix for edge problems in sampling secondaries'

Comment by Geant Build Server [ 20/Sep/16 ]

Harphool Kumawat mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 20/Sep/16 ]

Harphool Kumawat mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 20/Sep/16 ]

Harphool Kumawat mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 20/Sep/16 ]

Harphool Kumawat mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 20/Sep/16 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Readd defaulting of BACKEND.'

Comment by Geant Build Server [ 27/Sep/16 ]

Marilena Bandieramonte mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fix a compilation error from KNC'

Comment by Geant Build Server [ 27/Sep/16 ]

Marilena Bandieramonte mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fix for edge problems in sampling secondaries'

Comment by Geant Build Server [ 27/Sep/16 ]

Marilena Bandieramonte mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fix for edge problems in sampling secondaries'

Comment by Geant Build Server [ 27/Sep/16 ]

Marilena Bandieramonte mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 27/Sep/16 ]

Marilena Bandieramonte mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 27/Sep/16 ]

Marilena Bandieramonte mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 27/Sep/16 ]

Marilena Bandieramonte mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 06/Oct/16 ]

Andrei Gheata mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fix a compilation error from KNC'

Comment by Geant Build Server [ 06/Oct/16 ]

Andrei Gheata mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fix for edge problems in sampling secondaries'

Comment by Geant Build Server [ 06/Oct/16 ]

Andrei Gheata mentioned this issue in a commit of GeantV/geant:
'GEANT-102 fix for edge problems in sampling secondaries'

Comment by Geant Build Server [ 06/Oct/16 ]

Andrei Gheata mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 06/Oct/16 ]

Andrei Gheata mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 06/Oct/16 ]

Andrei Gheata mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 06/Oct/16 ]

Andrei Gheata mentioned this issue in a commit of GeantV/geant:
'GEANT-102 unused variables'

Comment by Geant Build Server [ 17/Jan/17 ]

Philippe Canal mentioned this issue in a commit of GeantV/geant:
'GEANT-102 Readd defaulting of BACKEND.'

Generated at Fri Apr 19 18:40:24 CEST 2019 using Jira 7.13.1#713001-sha1:5e06076c2d215a6f699b7e5c90ab2fae7ba5a1ce.