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

docs: use GitHub issues as the bug reporting address #6525

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

tredondo
Copy link
Contributor

No description provided.

Copy link
Collaborator

@rusty-snake rusty-snake left a comment

Choose a reason for hiding this comment

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

configure should not be edited directly, instead configure.ac should be edited and configure regenerated.

@kmk3 kmk3 added the documentation Issues and pull requests related to the documentation label Oct 30, 2024
@kmk3 kmk3 changed the title Update bug reporting address in configure docs: use GitHub issues as the bug reporting address Oct 30, 2024
Copy link
Collaborator

@kmk3 kmk3 left a comment

Choose a reason for hiding this comment

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

-# Copyright (C) 1992-1996, 1998-2017, 2020-2021 Free Software Foundation,
+# Copyright (C) various years Free Software Foundation,

It would not be helpful (to say the least) to remove information from a
copyright statement (especially for code you didn't write), so this change was
undone.

Additionally, note that this line is from another project, so it would
potentially also be a license violation.

Copy link
Collaborator

@kmk3 kmk3 left a comment

Choose a reason for hiding this comment

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

It looks like this parameter is intended to be an email address, probably to
allow people to contribute patches without needing an account, though I'm not
sure how often that happens.

We do not have a mailing list and the same email address is already listed on
README for reporting security vulnerabilities, so unless this email is used for
bug reports/patches, I suppose that it would make sense to reference just the
issue tracker.

@netblue30 Do you get bug reports/patches by email?

@kmk3 kmk3 requested a review from rusty-snake October 31, 2024 23:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Issues and pull requests related to the documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants