Re: [PATCH 1/5] fast-export: avoid using unnecessary language in a code comment
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 16, 2020, 21:05 UTC
- Message-ID
- <xmqqbli5whxn.fsf@gitster.c.googlers.com>
- In-Reply-To
- <587ddca42ae36be3d5b333cefe1f9af768bacc9a.1600279853.git.gitgitgadget@gmail.com>
"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 20 quoted lines
> 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
Obviously good change. Thanks.
> * referencing excluded commits, set the ref > * to the exact commit. Otherwise, the user > * wants the branch exported but every commit