From: bbitsch@ipfire.org
To: development@lists.ipfire.org
Subject: Re: [PATCH 2/4] unbound-dhcp-leases-bridge: Fix typo
Date: Mon, 21 Oct 2024 22:02:21 +0200 [thread overview]
Message-ID: <47ee1ae5-9bb0-4645-8a5d-0c369b0cf2b9@ipfire.org> (raw)
In-Reply-To: <6BF9FD99-2DC6-49B5-A763-BB14EB9D45A8@rymes.net>
[-- Attachment #1: Type: text/plain, Size: 2582 bytes --]
If I understand the rules cited, is it a user or an user? Just to choose an example, which is apparent frequently.
On 21.10.24 21:38, Tom Rymes <tom(a)rymes.net> wrote:
> If this is any help, I also always use “an” when in combination with an acronym that is pronounced with a vowel sound. I’d also say it isn’t terribly important, as mentioned already by Nick, and it doesn’t stick out to me as an error either way.
>
> FWIW, the same rule does apply with letter sounds: “an F” is the same as “an eff”.
>
> “…an FQDN…”
> “…an SOP…”
>
> “…a PDF…”
> “…a BFH…”
>
> I do wonder about “UFO”, and I wouldn’t say “an UFO”, so your guess is as good as mine there.
>
> I don’t think I cleared that up at all, but it’s English, so that’s probably par for the course and a sign I’m on the right track.
>
> Tom
>
> > On Oct 21, 2024, at 1:14 PM, Nick Howitt <nick(a)howitts.co.uk> wrote:
> >
> > Technically, I think this update is incorrect and "an" is correct - https://www.reddit.com/r/grammar/comments/riql6s/a_or_an_before_acronym_that_is_pronounced_with_a/ and https://www.grammar.com/a-vs-an-when-to-use. But TBH, I really don't think it is too important.
> >
> > Nick
> >
> >
> > On 21/10/2024 17:44, Bernhard Bitsch wrote:
> >>
> >> Reviewed-by: Bernhard Bitsch <bbitsch(a)ipfire.org> <mailto:bbitsch(a)ipfire.org>
> >>
> >> Am 21.10.2024 um 18:38 schrieb Michael Tremer:
> >>> Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org> <mailto:michael.tremer(a)ipfire.org>
> >>> ---
> >>> config/unbound/unbound-dhcp-leases-bridge | 4 ++--
> >>> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>>
> >>> diff --git a/config/unbound/unbound-dhcp-leases-bridge b/config/unbound/unbound-dhcp-leases-bridge
> >>> index bc944a073..2cbdaa004 100644
> >>> --- a/config/unbound/unbound-dhcp-leases-bridge
> >>> +++ b/config/unbound/unbound-dhcp-leases-bridge
> >>> @@ -279,9 +279,9 @@ class UnboundDHCPLeasesBridge(object):
> >>> self.unbound.update_dhcp_leases([l for l in self.leases if not l.has_expired()])
> >>> def _add_lease(self, lease):
> >>> - # Skip leases without an FQDN
> >>> + # Skip leases without a FQDN
> >>> if not lease.fqdn:
> >>> - log.debug("Skipping lease without an FQDN: %s" % lease)
> >>> + log.debug("Skipping lease without a FQDN: %s" % lease)
> >>> return
> >>> # Skip any leases that also are a static host
> >>
> >
>
>
>
next parent reply other threads:[~2024-10-21 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6BF9FD99-2DC6-49B5-A763-BB14EB9D45A8@rymes.net>
2024-10-21 20:02 ` bbitsch [this message]
[not found] <3b1760d6-2519-4a2d-874a-e2e6f0453027@howitts.co.uk>
2024-10-21 17:15 ` Michael Tremer
2024-10-21 16:38 [PATCH 1/4] unbound-dhcp-leases-bridge: Don't export expired leases to Unbound Michael Tremer
2024-10-21 16:38 ` [PATCH 2/4] unbound-dhcp-leases-bridge: Fix typo Michael Tremer
2024-10-21 16:44 ` Bernhard Bitsch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47ee1ae5-9bb0-4645-8a5d-0c369b0cf2b9@ipfire.org \
--to=bbitsch@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox