I have realized this mistake direct. I think I menage to solve it and has change some local settings to hopefully avoid that this happen again.
@s.neuhaus
I think you did a merge
instead of a rebase
, probably on the advice of the git
CLI which is confused by our workflow.
What you will ne...
I fixed this overlap in the last commit.
Hi @p.-a.loizeau,...
Hi @s.neuhaus...
-
c47afc79 · Add setup files for CFV and Day1
-
daae183e · Provide RICH CFV v23b, based on v23a
-
2e1b1fa3 · update setup_sis100_cfv with rich_v23b
- ... and 1 more commit. Compare 5524fdf3...2e1b1fa3
accepted
merge request
!297
"Provide RICH CFV v23b based on setup v23a"
at
CbmSoft / cbmroot_geometry
approved
merge request
!297
"Provide RICH CFV v23b based on setup v23a"
at
CbmSoft / cbmroot_geometry
commented on
merge request !297
"Provide RICH CFV v23b based on setup v23a"
at
CbmSoft / cbmroot_geometry
@f.kornas,...
-
d80e2c3f · fsd v25 geometries
- ... and 4 more commits. Compare 978685b9...d80e2c3f
commented on
merge request !297
"Provide RICH CFV v23b based on setup v23a"
at
CbmSoft / cbmroot_geometry
What is the reason that this is not merged yet? When will it be done?