[PATCH v3 1/5] fast-export: avoid using unnecessary language in a code comment
- From
Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
- Date
- Sep 26, 2020, 21:04 UTC
- Message-ID
- <587ddca42ae36be3d5b333cefe1f9af768bacc9a.1601154262.git.gitgitgadget@gmail.com>
- In-Reply-To
- <pull.734.v3.git.1601154262.gitgitgadget@gmail.com>
From: Johannes Schindelin <johannes.schindelin@gmx.de>
In an ongoing effort to avoid non-inclusive language, let's avoid using the branch name "master" in a code comment.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> --- builtin/fast-export.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/fast-export.c b/builtin/fast-export.c index 1b8fca3ee0..5527135ba8 100644 --- a/builtin/fast-export.c +++ b/builtin/fast-export.c @@ -1026,7 +1026,7 @@ static void handle_tags_and_duplicates(struct string_list *extras) /* * Getting here means we have a commit which * was excluded by a negative refspec (e.g. - * fast-export ^master master). If we are + * fast-export ^HEAD HEAD). If we are * referencing excluded commits, set the ref * to the exact commit. Otherwise, the user * wants the branch exported but every commit
-- gitgitgadget