From: Junio C Hamano <gitster@pobox.com>
To: Masanari Iida <standby24x7@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/4] [trivial] Fix comment typo
Date: Tue, 12 Nov 2013 09:19:00 -0800 [thread overview]
Message-ID: <xmqqob5pilmj.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1384269465-23352-1-git-send-email-standby24x7@gmail.com> (Masanari Iida's message of "Wed, 13 Nov 2013 00:17:42 +0900")
Masanari Iida <standby24x7@gmail.com> writes:
> Correct spelling typo
>
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
> git-bisect.sh | 2 +-
> pathspec.c | 4 ++--
> wrapper.c | 2 +-
> 3 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/git-bisect.sh b/git-bisect.sh
> index 9f064b6..ebac284 100755
> --- a/git-bisect.sh
> +++ b/git-bisect.sh
> @@ -137,7 +137,7 @@ bisect_start() {
> # cogito usage, and cogito users should understand
> # it relates to cg-seek.
> [ -s "$GIT_DIR/head-name" ] &&
> - die "$(gettext "won't bisect on seeked tree")"
> + die "$(gettext "won't bisect on sought tree")"
The phrasing before your "fix" comes from Cogito which called the
state cg-seek left in a "seeked tree", I think, so this change is
probably a wrong thing to do.
next prev parent reply other threads:[~2013-11-12 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 15:17 [PATCH 1/4] [trivial] Fix comment typo Masanari Iida
2013-11-12 15:17 ` [PATCH 2/4] [trivial] Fix typo in Documentation Masanari Iida
2013-11-12 15:17 ` [PATCH 3/4] [trivial] Fix typo in git-gui Masanari Iida
2013-11-12 17:36 ` Junio C Hamano
2013-11-12 15:17 ` [PATCH 4/4] [trivial] Fix spelling typo in contrib Masanari Iida
2013-11-12 17:19 ` Junio C Hamano [this message]
2013-11-12 17:41 ` [PATCH 1/4] [trivial] Fix comment typo Junio C Hamano
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=xmqqob5pilmj.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=standby24x7@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.