git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: zegolem <zegolem1383@outlook.fr>
To: git@vger.kernel.org
Cc: zegolem <zegolem1383@outlook.fr>
Subject: [PATCH] configure.ac: fix misspell in comments
Date: Thu,  5 Aug 2021 02:03:47 +0200	[thread overview]
Message-ID: <HE1PR05MB3371C8B2A590C32E0FDD212DD3F29@HE1PR05MB3371.eurprd05.prod.outlook.com> (raw)

There are two places in the file where 'you are' was written as 'your
are'.

Signed-off-by: ZIEGLER Florian <zegolem1383@outlook.fr>
---

Note: I didn't review the full file for other errors

 configure.ac | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/configure.ac b/configure.ac
index 031e8d3fee..44fd314a2e 100644
--- a/configure.ac
+++ b/configure.ac
@@ -955,7 +955,7 @@ else
 fi
 GIT_CONF_SUBST([NO_REGEX])
 #
-# Define FREAD_READS_DIRECTORIES if your are on a system which succeeds
+# Define FREAD_READS_DIRECTORIES if you are on a system which succeeds
 # when attempting to read from an fopen'ed directory.
 AC_CACHE_CHECK([whether system succeeds to read fopen'ed directory],
  [ac_cv_fread_reads_directories],
@@ -975,7 +975,7 @@ else
 fi
 GIT_CONF_SUBST([FREAD_READS_DIRECTORIES])
 #
-# Define SNPRINTF_RETURNS_BOGUS if your are on a system which snprintf()
+# Define SNPRINTF_RETURNS_BOGUS if you are on a system which snprintf()
 # or vsnprintf() return -1 instead of number of characters which would
 # have been written to the final string if enough space had been available.
 AC_CACHE_CHECK([whether snprintf() and/or vsnprintf() return bogus value],
-- 
2.32.0


             reply	other threads:[~2021-08-05  0:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05  0:03 zegolem [this message]
2021-08-05  1:34 ` [PATCH] configure.ac: fix misspell in comments Taylor Blau

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=HE1PR05MB3371C8B2A590C32E0FDD212DD3F29@HE1PR05MB3371.eurprd05.prod.outlook.com \
    --to=zegolem1383@outlook.fr \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).