Page MenuHomeFreeBSD

ping6: Rename options for unifying option parsing with ping
ClosedPublic

Authored by sucanjan_gmail.com on Aug 20 2019, 4:11 PM.

Details

Summary

Rename options for unifying option parsing with ping

The renaming is done so that names of equivalent options between ping and ping6 are the same, nonequivalent are different.

Submitted by: Ján Sučan <sucanjan@gmail.com>
Sponsored by: Google LLC (Google Summer of Code 2019)

Diff Detail

Repository
rS FreeBSD src repository
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

asomers requested changes to this revision.Aug 20 2019, 4:56 PM
asomers added inline comments.
sbin/ping6/ping6.8
32 ↗(On Diff #61052)

You should update this date.

43 ↗(On Diff #61052)

This line was sorted alphabetically before. You should try to keep it that way.

59 ↗(On Diff #61052)

IPv6 hoplimit is functionally equivalent to IPv4 TTL, so they can use the same flag.

312 ↗(On Diff #61052)

I suggest changing -w to -y to preserve the current symmetry between -w and -W. You would of course need to choose a different letter for "Generate ICMPv6 Note Information supported"

sbin/ping6/ping6.c
437 ↗(On Diff #61052)

What was the base revision from which you generated this diff? There should've been a case 'H' here.

This revision now requires changes to proceed.Aug 20 2019, 4:56 PM
sbin/ping6/ping6.c
437 ↗(On Diff #61052)

I genereated this from my local git branch with D21338 applied.

Update date in the manual page.
Sort options in the SYNOPSIS section of the manual page alphabetically.
Use -m for hoplimit.
Change -w to -y.
Sort the getopt string alphabetically.
Sort options in the usage message alphabetically.
Reflect change of the -X option name to the test.

sbin/ping6/ping6.8
32 ↗(On Diff #61052)

Fixed.

43 ↗(On Diff #61052)

Fixed.

59 ↗(On Diff #61052)

Fixed.

312 ↗(On Diff #61052)

Fixed.

asomers accepted this revision.Aug 23 2019, 3:16 PM
This revision is now accepted and ready to land.Aug 23 2019, 3:16 PM

One more thing: you should normally add an entry in UPDATING letting people know that the options have changed so they can update their scripts. I'll go ahead and write it this time.

This revision was automatically updated to reflect the committed changes.