diff options
| author | Karl Williamson <public@khwilliamson.com> | 2011-11-10 20:58:48 -0700 |
|---|---|---|
| committer | Karl Williamson <public@khwilliamson.com> | 2011-11-10 21:03:42 -0700 |
| commit | de37f83fbb716d5a1b970c4302ba4c852671d54b (patch) | |
| tree | 8583d1f5fe69a72e62140daf3b844202bcab9321 /t | |
| parent | 461020ad235958b138a5f0a460f133d203eee293 (diff) | |
| download | perl-de37f83fbb716d5a1b970c4302ba4c852671d54b.tar.gz | |
podcheck.t: Add comment
This is in response to Tony Cook's noticing that the sort order changed,
but the data file was left in the old order. The next time someone
changed things and did a regen, it got sorted, but the git diff showed
more changes, as a result, than there actually were in that commit.
Diffstat (limited to 't')
| -rw-r--r-- | t/porting/podcheck.t | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/t/porting/podcheck.t b/t/porting/podcheck.t index dbf6fb9d31..46b6eac97a 100644 --- a/t/porting/podcheck.t +++ b/t/porting/podcheck.t @@ -1680,7 +1680,9 @@ if (! $has_input_files) { } # If regenerating the data file, start with the modules for which we don't -# check targets +# check targets. If you change the sort order, you need to run --regen before +# committing so that future commits that do run regen don't show irrelevant +# changes. if ($regen) { foreach (sort { lc $a cmp lc $b } keys %valid_modules) { my_safer_print($copy_fh, $_, "\n"); |