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

Please consider making Changes file more parser friendly #66

Open
luzpaz opened this issue Jan 10, 2024 · 2 comments
Open

Please consider making Changes file more parser friendly #66

luzpaz opened this issue Jan 10, 2024 · 2 comments

Comments

@luzpaz
Copy link

luzpaz commented Jan 10, 2024

At the time of this ticket the Changes file has non-uniform patterns to parse

Screenshot_20240110_151146

Would you consider following recommendations from https://keepachangelog.com or at least a minimal form of it.

Perhaps putting the date and version on the same line at least ?

@prigaux
Copy link
Collaborator

prigaux commented Jan 10, 2024

Hi. Why not. But there are already git tags. Could you precise why you need parsing the Changes?

@luzpaz
Copy link
Author

luzpaz commented Jan 10, 2024

Sure, see http://freshcode.club/submit/hexedit

Screenshot_20240110_180251

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

No branches or pull requests

2 participants