Date: Fri, 29 Dec 2023 12:29:06 GMT From: Benedict Reuschling <bcr@FreeBSD.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org Subject: git: 019719eb08 - main - Remove redundancy: more complete -> complete Message-ID: <202312291229.3BTCT6fY000358@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch main has been updated by bcr: URL: https://cgit.FreeBSD.org/doc/commit/?id=019719eb085172ae2dcf150b50fc467c66331347 commit 019719eb085172ae2dcf150b50fc467c66331347 Author: Benedict Reuschling <bcr@FreeBSD.org> AuthorDate: 2023-12-29 12:28:20 +0000 Commit: Benedict Reuschling <bcr@FreeBSD.org> CommitDate: 2023-12-29 12:28:20 +0000 Remove redundancy: more complete -> complete --- documentation/content/en/articles/committers-guide/_index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc index 6caa7d6bf4..9204c649a9 100644 --- a/documentation/content/en/articles/committers-guide/_index.adoc +++ b/documentation/content/en/articles/committers-guide/_index.adoc @@ -816,7 +816,7 @@ That is OK. Do not panic. Instead, handle them the same as any other merge conflicts. To keep it simple, I will just describe a common issue that may arise. -A pointer to a more complete treatment can be found at the end of this section. +A pointer to a complete treatment can be found at the end of this section. Let's say the includes changes upstream in a radical shift to terminfo as well as a name change for the option. When you updated, you might see something like this:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202312291229.3BTCT6fY000358>