-
Notifications
You must be signed in to change notification settings - Fork 577
instructions on how to patch Configure unclear #16062
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
Comments
From @maukeCreated by @maukeA comment at the beginning of Configure says: # Though this script was generated by metaconfig from metaunits, it is But pod/perlhack.pod says nothing about patching Configure. - What does it mean to "send patches"? (Attach them to a bug ticket? Mail them Perl Info
|
From @TuxOn Sun, 02 Jul 2017 00:14:57 -0700, "l.mai@web.de (via RT)"
Good point. If docs are added there, I'd like to have a statement like "Patching Configure should be a last resort, as it is shared between
Acceptable
Acceptable
Acceptable on the condition that I (or my co-maints) am/are notified
At this moment, yes. But there is at least arc to help me: he knows -- |
The RT System itself - Status changed from 'new' to 'open' |
Migrated from rt.perl.org#131688 (status was 'open')
Searchable as RT131688$
The text was updated successfully, but these errors were encountered: