git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/2] git-gui: Fix a loose/lose mistake

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 18, 2012, 20:24 UTC
Message-ID
<7vsjbkrlsv.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1345280851-6626-1-git-send-email-bbolli@ewanet.ch>
Beat Bolli <bbolli@ewanet.ch> writes:
Show 20 quoted lines
> 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?
Previous: Pat ThoytsNext: Pat Thoyts
Message 5 of 6 in “git-gui: Fix a loose/lose mistake”
  1. 1/2 git-gui: Fix a loose/lose mistakeBeat Bolli, Aug 18, 2012
  2. 2/2 git-gui: remove .git/CHERRY_PICK_HEAD after committingBeat Bolli, Aug 18, 2012
  3. Junio C HamanoAug 18, 2012
  4. Pat ThoytsSep 17, 2012
  5. Junio C HamanoAug 18, 2012
  6. Pat ThoytsSep 17, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.