diff options
| author | Rich Salz <rsalz@akamai.com> | 2015-08-17 15:21:33 -0400 |
|---|---|---|
| committer | Rich Salz <rsalz@openssl.org> | 2015-08-21 15:11:50 -0400 |
| commit | 9b86974e0c705ea321ddbc9a9d8562c894809e5b (patch) | |
| tree | 69b6437896ca7728ebec6b7d3be7b217149d9862 /doc/apps/asn1parse.pod | |
| parent | 3da9505dc02b0594633c73a11343f54bb5dbf536 (diff) | |
Fix L<> content in manpages
L<foo|foo> is sub-optimal If the xref is the same as the title,
which is what we do, then you only need L<foo>. This fixes all
1457 occurrences in 349 files. Approximately. (And pod used to
need both.)
Reviewed-by: Richard Levitte <levitte@openssl.org>
Diffstat (limited to 'doc/apps/asn1parse.pod')
| -rw-r--r-- | doc/apps/asn1parse.pod | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/apps/asn1parse.pod b/doc/apps/asn1parse.pod index b44fb9fd3d..afe94b09d8 100644 --- a/doc/apps/asn1parse.pod +++ b/doc/apps/asn1parse.pod @@ -83,7 +83,7 @@ option can be used multiple times to "drill down" into a nested structure. =item B<-genstr string>, B<-genconf file> generate encoded data based on B<string>, B<file> or both using -L<ASN1_generate_nconf(3)|ASN1_generate_nconf(3)> format. If B<file> only is +L<ASN1_generate_nconf(3)> format. If B<file> only is present then the string is obtained from the default section using the name B<asn1>. The encoded data is passed through the ASN1 parser and printed out as though it came from a file, the contents can thus be examined and written to a @@ -189,6 +189,6 @@ ASN.1 types is not well handled (if at all). =head1 SEE ALSO -L<ASN1_generate_nconf(3)|ASN1_generate_nconf(3)> +L<ASN1_generate_nconf(3)> =cut |