From: Christopher Head Date: Tue, 10 Feb 2026 01:22:12 +0000 (-0800) Subject: Fix order of class/type in resolve man page X-Git-Tag: v257.11~42 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=a2933ff5ecfaea313840dccbd326355bfa7cc8d6;p=thirdparty%2Fsystemd.git Fix order of class/type in resolve man page For each RR `ResolveRecord` returns, it returns the class before the type, not after. (cherry picked from commit 8ae4aa26c181cf20c9e613074d2e47ddf58dd82d) (cherry picked from commit c50b34abe36b323697e291c22f79ac6350306f16) (cherry picked from commit cbc1697b9a11128581b6367b18dd5ddc59bcbfa5) --- diff --git a/man/org.freedesktop.resolve1.xml b/man/org.freedesktop.resolve1.xml index 324b6888537..362e17f0556 100644 --- a/man/org.freedesktop.resolve1.xml +++ b/man/org.freedesktop.resolve1.xml @@ -285,7 +285,7 @@ node /org/freedesktop/resolve1 { (no IDNA conversion is applied), followed by the 16-bit class and type fields (which may be ANY). Finally, a flags field may be passed in to alter behaviour of the look-up (see below). On completion, an array of RR items is returned. Each array entry consists of the network interface - index the RR was discovered on, the type and class field of the RR found, and a byte array of the raw + index the RR was discovered on, the class and type field of the RR found, and a byte array of the raw RR discovered. The raw RR data starts with the RR's domain name, in the original casing, followed by the RR type, class, TTL and RDATA, in the binary format documented in RFC 1035. For RRs that support name