-
Notifications
You must be signed in to change notification settings - Fork 5
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
Light maintenance #1
Conversation
Nobody use that anymore.
At the time of making that change, tests have been failing for a long (?) time due to a change in golang parsing. When that code was written, fmt.Sscanf was accepting 0x and -0x (without digit), which is why the original author also accepted it in the config parsing. This is not the case anymore, and this commit only reflect the reality of things.
Co-authored-by: Hidde Beydals <hiddeco@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few nits to align with versions on go-git
.
Co-authored-by: Paulo Gomes <paulo.gomes.uk@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @MichaelMure 🙇
BTW, I found out about two maintained fork of The first one apparently has a very very nice capability: being able to edit a config file without deleting the comments a user might have put there. It would be great to cherry pick those commits. See for example git-bug/git-bug#1022 how that can cause problems. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @MichaelMure!
@MichaelMure as for the changes in other forks, it would be better to ask the authors whether they want to upstream their changes. |
This PR is a form of light maintenance on this repo. Details are in each commit, but TL;DR: