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

Need 'this is a generated file, DO NOT EDIT' warnings #133

Closed
389-ds-bot opened this issue Sep 12, 2020 · 5 comments
Closed

Need 'this is a generated file, DO NOT EDIT' warnings #133

389-ds-bot opened this issue Sep 12, 2020 · 5 comments
Labels
closed: won't fix Migration flag - Issue
Milestone

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/133


https://bugzilla.redhat.com/show_bug.cgi?id=241090

Description of problem:
Each of the generated files needs a note at the top to warn potential
developers
that these files will be regenerated.

Version-Release number of selected component (if applicable):
current CVS

How reproducible:
edit (for example) ds_newinst.pl instead of ds_newinst.pl.in

Actual results:
Edit wrong file - work potentially lost

Expected results:
Some way to know I was editing the wrong file

Additional info:
@389-ds-bot 389-ds-bot added the closed: won't fix Migration flag - Issue label Sep 12, 2020
@389-ds-bot 389-ds-bot added this to the FUTURE milestone Sep 12, 2020
@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2012-01-10 06:05:49

batch update to FUTURE milestone

@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2012-08-14 19:56:22

set default ticket origin to Community

@389-ds-bot
Copy link
Author

Comment from nkinder (@nkinder) at 2012-08-28 04:14:49

Added initial screened field value.

@389-ds-bot
Copy link
Author

Comment from nkinder (@nkinder) at 2017-02-11 23:08:45

Metadata Update from @nkinder:

  • Issue set to the milestone: FUTURE

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2019-08-23 22:15:09

Metadata Update from @mreynolds389:

  • Custom field reviewstatus adjusted to None (was: Needs Review)
  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: won't fix Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant