Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove BinaryFormatter. Fixes #9150 #9344

Merged

Conversation

GintasS
Copy link
Collaborator

@GintasS GintasS commented Jul 7, 2021

Fixes #9150

Proposed changes

  • Removed BinaryFormatter code after @pmiossec discovery.

Test methodology

  • Current tests were used.

Test environment(s)

GIT 2.21.0.windows.1
Windows 10


✒️ I contribute this code under The Developer Certificate of Origin.

@ghost ghost assigned GintasS Jul 7, 2021
@GintasS
Copy link
Collaborator Author

GintasS commented Jul 7, 2021

Same tests fail on this one too locally, so I'm going to disregard them.

image

@GintasS GintasS force-pushed the investigate_binary_formatter_9150 branch 4 times, most recently from c5bbb31 to 953accb Compare July 7, 2021 15:08
Copy link
Member

@pmiossec pmiossec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder only on the commit message that I find misleading.

Is something like that better?

"Remove no more used BinaryFormatter for commit template"

@GintasS GintasS force-pushed the investigate_binary_formatter_9150 branch from 953accb to 09724ea Compare July 8, 2021 14:14
@GintasS
Copy link
Collaborator Author

GintasS commented Jul 8, 2021

I wonder only on the commit message that I find misleading.

Is something like that better?

"Remove no more used BinaryFormatter for commit template"

Done.

@GintasS
Copy link
Collaborator Author

GintasS commented Jul 9, 2021

Should I commit something or how can I rerun a AppVeyor build? Seems to fail for no reason, at least not in regards to this PR.

@pmiossec
Copy link
Member

pmiossec commented Jul 9, 2021

Should I commit something or how can I rerun a AppVeyor build? Seems to fail for no reason, at least not in regards to this PR.

I have re-launched the build of the PR. Failed again.

I don't know if it is linked to #9273 (comment)

If that is the case, could you rebase your work on top of updated master.

Note: to trigger again a build, you could close and then reopen the PR.

@GintasS
Copy link
Collaborator Author

GintasS commented Jul 9, 2021

Should I commit something or how can I rerun a AppVeyor build? Seems to fail for no reason, at least not in regards to this PR.

I have re-launched the build of the PR. Failed again.

I don't know if it is linked to #9273 (comment)

If that is the case, could you rebase your work on top of updated master.

Note: to trigger again a build, you could close and then reopen the PR.

Will try. Thanks!

@GintasS GintasS force-pushed the investigate_binary_formatter_9150 branch from 09724ea to 6330388 Compare July 9, 2021 15:20
@pmiossec
Copy link
Member

pmiossec commented Jul 9, 2021

It seems to have worked. I think we are good to merge it...

@mstv mstv merged commit c3218cd into gitextensions:master Jul 9, 2021
@ghost ghost added this to the 3.6 milestone Jul 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Resolve SYSLIB0011 / replace BinaryFormatter
4 participants