Removing uuid feature #409
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
So I do thing wie should do this, now that we have a 5.0 released that still supports it (and we can still backport fixes for some time to come). Moving forward, loosing some code |
sschleemilch
approved these changes
Oct 14, 2024
|
MoM:
|
|
MoM: Merge |
Note: Keeping UUID as bit in binary output Signed-off-by: Erik Jaegervall <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This would be the last step in removing the old UUID functionality. I have generally tried to remove UUID support in all tools, i.e. fields/columns with UUID are removed. One exception though - I am keeping the UUID byte for binary output as I believes tools using that format (VISSR) could have difficult handling a changd format.
What I would like to bring up in a VSS meeting