Release 5.4 update gdcm#6059
Release 5.4 update gdcm#6059thewtex wants to merge 3 commits intoInsightSoftwareConsortium:release-5.4from
Conversation
No longer present.
Code extracted from:
https://github.com/malaterre/GDCM.git
at commit dacccb6c04ee13f6958359c193f804358f4672d7 (release).
* upstream-GDCM: GDCM 2026-03-10 (dacccb6c)
|
Too many files changed for review. ( |
|
One concern I have is when this branch in merged into release and then main. The main branch can be merged with "ours" stragegy to ensure that the changes here don't effect release/main. However, the gdcm sub-tree will have different commits it's unclear to me how best to manage this. @bradking Any advice on how to manage the sub-tree for updated to a release branch? |
|
The |
|
That seems like regular issue with the release-5.4 not being merged into release and main branches |
hjmjohnson
left a comment
hjmjohnson
left a comment
There was a problem hiding this comment.
I have no problems with this approach. A careful merge into upstream/main might be needed, but that should not be hard to accomplish.
|
We are queuing a number of patches on |
4 participants
Updating GDCM to the current
releasebranch on ITKrelease-5.4.