From: Junio C Hamano <gitster@pobox.com>
To: Pat Thoyts <patthoyts@users.sourceforge.net>
Cc: git@vger.kernel.org, Beat Bolli <bbolli@ewanet.ch>
Subject: Re: [PATCH 1/2] git-gui: Fix a loose/lose mistake
Date: Sat, 18 Aug 2012 13:24:00 -0700 [thread overview]
Message-ID: <7vsjbkrlsv.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1345280851-6626-1-git-send-email-bbolli@ewanet.ch> (Beat Bolli's message of "Sat, 18 Aug 2012 11:07:30 +0200")
Beat Bolli <bbolli@ewanet.ch> writes:
> No po update needed, as this string is untranslated.
>
> Signed-off-by: Beat Bolli <bbolli@ewanet.ch>
> ---
> git-gui/lib/commit.tcl | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/git-gui/lib/commit.tcl b/git-gui/lib/commit.tcl
> index 0d81432..78c5eeb 100644
> --- a/git-gui/lib/commit.tcl
> +++ b/git-gui/lib/commit.tcl
> @@ -268,7 +268,7 @@ proc commit_commitmsg {curHEAD msg_p} {
> && [is_config_true gui.warndetachedcommit]} {
> set msg [mc "You are about to commit on a detached head.\
> This is a potentially dangerous thing to do because if you switch\
> -to another branch you will loose your changes and it can be difficult\
> +to another branch you will lose your changes and it can be difficult\
> to retrieve them later from the reflog. You should probably cancel this\
> commit and create a new branch to continue.\n\
> \n\
Looks obviously correct; Pat?
next prev parent reply other threads:[~2012-08-18 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 9:07 [PATCH 1/2] git-gui: Fix a loose/lose mistake Beat Bolli
2012-08-18 9:07 ` [PATCH 2/2] git-gui: remove .git/CHERRY_PICK_HEAD after committing Beat Bolli
2012-08-18 20:28 ` Junio C Hamano
2012-09-17 11:52 ` Pat Thoyts
2012-08-18 20:24 ` Junio C Hamano [this message]
2012-09-17 10:54 ` [PATCH 1/2] git-gui: Fix a loose/lose mistake Pat Thoyts
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=7vsjbkrlsv.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bbolli@ewanet.ch \
--cc=git@vger.kernel.org \
--cc=patthoyts@users.sourceforge.net \
/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 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 NNTP newsgroup(s).