summaryrefslogtreecommitdiff
path: root/pod/perlhack.pod
Commit message (Collapse)AuthorAgeFilesLines
* Change various search.cpan.org references to metacpan.org and www.cpan.orgDan Book2020-02-111-4/+4
| | | | (cherry picked from commit c23f766f6c261b334740784b1baca327e8118a87)
* Update documentation, readmes, comments, and utilities to reference the ↵Dan Book2020-02-111-6/+3
| | | | | | | | GitHub issue tracker The perlbug utility and perlbug@perl.org should no longer be used to submit bug reports or patches. (cherry picked from commit 8166b4e0bc220e759aa233af54ac1e60cc510f0c)
* Update perlgit and perlhack to reference GitHub pull request workflowDan Book2019-10-271-35/+29
| | | | (cherry picked from commit 617d9ec40b6f4f34796deb5007320a135e402779)
* Update documentation, comments, metadata to reference GitHub as canonical ↵Dan Book2019-10-271-8/+7
| | | | | | | | | | | | | | | | | | repository (#1186) * Update repository and bugtracker URLs to GitHub in makemeta regen META files * Update POD and comments to reference GitHub as canonical repository * Update Porting/corelist.pl to recognize GitHub issue tracker * remove "A note on camel and dromedary" * Remove redundant 'Committing your changes' section (cherry picked from commit 47ef154c59e75e9351d27b3bd06d6ac57494193c)
* Revise inclusion of name and email in Git historyv5.28.0Sawyer X2018-06-221-1/+2
|
* trailing spaces drive me nutsSawyer X2018-06-221-1/+1
|
* Clarify your name and email *will* appear in AUTHORS unless asked:Sawyer X2018-06-201-0/+9
| | | | | | | | Neil Bowers and Andreas Koenig spotted that, based on GDPR, we should clarify to people that their name and email will appear in AUTHORS when submitting a patch and that it can be removed when asked. Neil contributed the phrasing.
* RT#132520: mention it's OK to attach a patch to an RT ticketMarco Fontani2017-11-301-0/+3
| | | | | | | | | ... as was the case of my first patch to perl: I tried to find my use case in perlhack.pod, failed, and "hoped for the best". With this, perlhack makes clearer that attaching a patch to an already existing RT ticket is a perfectly valid and accepted use-case for getting patches into perl - same as using perlbug.
* When and how to use Devel::PatchPerl to repair older builds.James E Keenan2017-06-011-0/+49
| | | | Following recommendation by Matthew Horsfall.
* pods: Add L<> for links missing them; a couple nitsKarl Williamson2017-04-051-3/+3
|
* Added some discussion of tabs & spaces in the source codeAndy Lester2016-10-311-2/+7
|
* fix more file pathsLukas Mai2016-01-101-1/+1
|
* fix list rendering in perlhackKaren Etheridge2015-09-091-2/+2
| | | | | | | | | | | | | | | At http://perldoc.perl.org/perlhack.html#TESTING, this was rendering as: 1 ) These select Unicode rules.... 2 ) If you use the form... For: RT #126021
* perlhack: Nits and update for v5.22Karl Williamson2015-04-181-6/+11
|
* Add text about EBCDIC to pods: perlhack* perlportKarl Williamson2015-01-141-3/+51
|
* add Porting/bench.plDavid Mitchell2014-11-291-0/+21
| | | | | | | | | | | | | | | | | | | This tool runs code snippets found in t/perf/benchmarks (or similar) under cachegrind, in order to calculate how many instruction reads, data writes, branches, cache misses, etc. that one execution of the snippet uses. It will run them against two or more perl executables and show how much each test has gotten better or worse. It is modelled on the perlbench tool, but since it measures instruction reads etc., rather than timings, it is much more precise and reproducible. It is also considerably faster, and is capable or running tests in parallel. Rather than displaying a single relative percentage per test/perl combination, it displays values for 13 different measurements, such as instruction reads, conditional branch misses etc. This commit also changes the format of t/perf/benchmarks slightly; it becomes an AoH rather than a HoH (to allow checking for duplicate keys), and the test names themselves become a :: hierarchy.
* Update Perl 5 Porter list archives.James E Keenan2014-10-171-2/+1
| | | | For: RT # 122996
* Mention perlbug -p in perlhack.Craig A. Berry2014-01-171-11/+9
| | | | | Using git's --attach with perlbug -f actually mangled the patches, making them harder to apply, but now we have a better way to do it.
* Correct URL for github.com mirror of Perl 5 repository.Martin McGrath2013-12-191-1/+1
| | | | | | Add Martin McGrath to AUTHORS. For: RT #120819
* perlhack.pod: consistent spaces after dotsFather Chrysostomos2013-11-011-2/+2
|
* perlhack: Make MAINTENANCE BRANCHES a linkFather Chrysostomos2013-09-171-1/+1
|
* add reference to maintenance branches in perlpolicyChristian Millour2013-09-171-1/+2
|
* Multiple commits in 1 attachment in Patch GuideSmylers2013-09-051-19/+8
| | | | | | | | | | | In the Super Quick Patch Guide, if a change involves multiple commits, put them all in a single perlbug attachment. Father Chrysostomos says it's easier like this, in a comment on RT #119599. It simplifies the instructions, and avoiding the need to mention mail clients.
* When sending an email manually so it can have multiple patches, point outSmylers2013-09-051-1/+4
| | | | | | | | | | | | | | | | that Mutt can construct the email for you. Obviously this isn't as generally relevant as the rest of the Guide, since patchers will use many different mail clients. But it's a significant boon for those who do use Mutt, and a very short addition to the Guide. Mutt is singled out simply because it has this functionality; I suspect that most other widely used mail clients don't. Committer: Removed trailing whitespace. Applied patch manually because other lines in the file had been rebroken and patch no longer applied cleanly. For: RT #119599
* Multiple commits in Super Quick Patch GuideSmylers2013-09-051-0/+17
| | | | | | | | | | | | How to use perlbug when a change is a series of commits, not a single commit. This is the advice RJBS gave me over IRC. Including it in the guide should avoid him having to repeat the advice to others. Committer: Added single quotes around one keyboard command. For: RT #119599
* Resetting a check out in Super Quick Patch GuideSmylers2013-09-051-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | Add advice so that somebody wishing to submit a second patch doesn't need to throw away their perl check-out and start again. Not knowing the 'git clean' step caught me out, and meant perl wouldn't build for me. Nicholas helped me out. Adding this to the guide will hopefully save Nicholas from having to repeat that for others (especially since others may not be fortunate enough to have Nicholas handily seated next to them at the point they encounter it). (The non-building was because some things in the repository had been re-arranged since my previous patch (several months earlier), and the latest build was getting confused by some files left over from a pre-re-arragned build.) The 'git clean' step will also remove the first 0001-*.patch file, avoiding the problem of there being two files matching that glob when attaching the second patch. Committer: Removed trailing whitespace. For: RT #119599
* Suggest reading blead's Super Quick Patch GuideSmylers2013-09-051-0/+7
| | | | | | | | | | | | | | | The Super Quick Patch Guide has been improved several times. Suggest that a patcher looks at the latest version in the checkout of blead they've just made, in case that's been improved since whichever released version they were reading. This has caught me out before: I've done something sub-optimal (for me or those reviewing my patches) by diligently following out-of-date instructions. Remove trailing whitespace. For: RT #119599
* perlbug command wrapped to fit in 79 columnsSmylers2013-09-051-1/+2
| | | | | | | | | | | | To pass t/porting/podcheck.t --pedantic The line-break is inside a $(...), so the lines can be copied-and-pasted as they are, complete with line-break and extra spaces, and still give the same output. Remove trailing whitespace. For: RT #119599
* Have perlbug report version being patchedSmylers2013-09-051-1/+1
| | | | | | | | | In the Super Quick Patch Guide, run the perlbug and perl from the working copy that the patch is against, so the bug report contains relevant version and configuration data, rather than that of whichever system perl the reporter happens to have installed. For: RT #119599
* Consistent indent on shell commandsSmylers2013-09-051-9/+9
| | | | | | | | | Most verbatim lines with shell commands had 2 spaces before the % prompt. A few had 1 or 4 spaces. Make them all 2. Remove trailing whitespace. For: RT #119599
* perlhack.pod tidiedSmylers2013-09-051-43/+44
| | | | | | | | | In accordance with the comment at the top of the file, before I make other changes to it. Remove trailing whitespace. For: RT #119599
* Consistent spaces after dots in perlhack.podFather Chrysostomos2013-07-041-106/+106
|
* Remove various rarely used test targets from the generated Makefile.Nicholas Clark2013-07-011-44/+1
| | | | | | | | | | | | | | Remove these targets and their documentation: check.third check.utf16 check.utf8 coretest minitest.utf16 test.deparse test.taintwarn test.third test.torture test.utf16 test.utf8 test_notty.deparse test_notty.third test_prep.third torturetest ucheck ucheck.third ucheck.utf16 ucheck.valgrind utest utest.third utest.utf16 utest.valgrind It's still possible to run the actions these targets "by hand", if desired. This commit simply removes the convenience targets from the Makefile, reducing its complexity.
* Fixed verbatim lines in POD over 79 charactersBrian Gottreu2013-06-221-2/+2
|
* perlhack: in-line functions need extra careKarl Williamson2012-12-231-0/+9
|
* Removed p5p-faq reference from perlhack.pod.Augustina Blair2012-12-231-7/+0
| | | | | Original document linked to has been removed because it was out of date and redundant.
* Adjust MANIFEST, Makefiles, test harnesses, documentation, etc., aware of newJames E Keenan2012-12-071-6/+5
| | | | | | directory t/opbasic. For RT #115838
* perlhack: Add note to not use "register" declarationsKarl Williamson2012-11-241-0/+6
|
* perlhack: better wordFather Chrysostomos2012-11-201-2/+2
| | | | At Aristotle’s suggestion
* perlhack: Note why some t/op tests avoid test.plFather Chrysostomos2012-11-181-0/+3
|
* add a directory of tests to run with large available memoryTony Cook2012-05-211-0/+7
| | | | Intended for testing 64-bit behavious
* Revert "Put Jesse's "How a Bill Becomes a Law" into perlhack (with editing)"Dave Rolsky2011-09-161-50/+2
| | | | This reverts commit 6a945912f2861921b440402072b7053a1dc414a5.
* Add a mention of #p5p to perlhackDave Rolsky2011-09-151-0/+6
|
* Put Jesse's "How a Bill Becomes a Law" into perlhack (with editing)Dave Rolsky2011-09-151-2/+50
|
* Wording tweak to clarify that perlbug submits the patch for you via emailDave Rolsky2011-09-151-2/+2
|
* Run podtidy on perlhack.podDave Rolsky2011-09-151-20/+22
|
* Add another explicit synonym for the porters.Jesse Vincent2011-08-161-1/+1
|
* More typo fixes in pod/perl*.pod filesKeith Thompson2011-07-311-1/+1
|
* Expand "git co" in pod/perlhack.podbrian greenfield2011-07-071-1/+1
|
* perlhack: Change some C<> into F<>Karl Williamson2011-06-211-1/+1
|
View Lorry Controller Status