diff options
| author | Jim Cromie <jim.cromie@gmail.com> | 2010-06-16 20:38:12 -0600 |
|---|---|---|
| committer | Florian Ragwitz <rafl@debian.org> | 2010-09-16 02:55:12 +0200 |
| commit | b28e2c3cb7448b983edc991b66c9eb650488d89b (patch) | |
| tree | 222924c364ffe73204c001b162333f453ae96b46 | |
| parent | ab296a20b432e195903c2794a3ea834e03f0134b (diff) | |
| download | perl-b28e2c3cb7448b983edc991b66c9eb650488d89b.tar.gz | |
'make regen' really shouldn't be special
Revert 'make regen' special case advice of
94e892a68016a417b1b324213d39309b8b744d0e, leave the minor whitespace cleanup.
| -rw-r--r-- | pod/perlrepository.pod | 11 |
1 files changed, 0 insertions, 11 deletions
diff --git a/pod/perlrepository.pod b/pod/perlrepository.pod index 671529f03b..f369addb7a 100644 --- a/pod/perlrepository.pod +++ b/pod/perlrepository.pod @@ -473,17 +473,6 @@ $install_root/lib. If you are unsure about the proper location of a file that may have gotten copied while building the source distribution, consult the C<MANIFEST>. -As a special case, several files are regenerated by 'make regen' if -your patch alters C<embed.fnc>. These are needed for compilation, but -are included in the distribution so that you can build perl without -needing another perl to generate the files. You must test with these -regenerated files, but it is preferred that you instead note that 'make -regen is needed' in both the email and the commit message, and submit -your patch without them. If you're submitting a series of patches, it -might be best to submit the regenerated changes immediately after the -source-changes that caused them, so as to have as little effect as -possible on the bisectability of your patchset. - =for XXX What should we recommend about binary files now? Do we need anything? |