Bug#485467: see also diagnostics

jidanni at jidanni.org jidanni at jidanni.org
Thu Jun 18 20:59:43 UTC 2009


|I tried to post all the following to http://support.github.com/discussions/
|but just got "The change you wanted was rejected."
|>>>>> "bdf" == brian d foy <brian at stonehenge.com> writes:
|bdf> On Sun, Jun 14, 2009 at 3:14 AM, <jidanni at jidanni.org> wrote:
|>> On perldiag(1) SEE ALSO, could you add "diagnostics" (after warnings, perllexwarn.)
|>> I have no way of reporting this. Thanks.
|bdf> Here's what you can do:
|bdf> * fork perl on github.
|bdf> * make the change
|bdf> * send a pull request, which will come from github's email address
|This all sounds way too complicated for me. All I want to do is send
|someone a patch to add one line to the perldiag man page. Can someone
|give me the URL to the current version of the source file, and tell me
|who to then send the patch to? I don't want to download many files or
|have to learn how to set up a git server. Thanks.
|Maybe I even have the current version
|$ dlocate --filename-only perldiag|xargs wc|sed 2q
|   258   1467  68608 /usr/share/man/man1/perldiag.1.gz
|  5037  30157 181950 /usr/share/perl/5.10.0/pod/perldiag.pod
>>>>> "bdf" == brian d foy <brian at stonehenge.com> writes:
bdf> On Thu, Jun 18, 2009 at 3:42 PM, <jidanni at jidanni.org> wrote:
>> This all sounds way too complicated for me.
bdf> There's nothing more I can do for you.






More information about the Perl-maintainers mailing list