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

Re: [PATCH] git-gui: stop using deprecated merge syntax

From
Pat Thoyts <patthoyts@users.sourceforge.net>
Date
Oct 3, 2016, 23:15 UTC
Message-ID
<87int9t46a.fsf@red.patthoyts.tk>
In-Reply-To
<5283506a-9399-6ddc-d714-1dd9d2b49704@web.de>
René Scharfe <l.s.r@web.de> writes:
Show 31 quoted lines
>Am 03.10.2016 um 10:30 schrieb Pat Thoyts:
>> The only problem I see here is that generally git-gui tries to continue
>> to work with older versions of git as well. So adding a guard using the
>> git-version procedure should maintain that backwards compatibility.
>
>Makes sense for a stand-alone tool.
>
>> I suggest:
>>
>> From c2716458f05893ca88c05ce211a295a330e74590 Mon Sep 17 00:00:00 2001
>> From:  René Scharfe <l.s.r@web.de>
>> Date: Sat, 24 Sep 2016 13:30:22 +0200
>> Subject: [PATCH] git-gui: stop using deprecated merge syntax
>>
>> Starting with v2.5.0 git merge can handle FETCH_HEAD internally and
>> warns when it's called like 'git merge <message> HEAD <commit>' because
>> that syntax is deprecated.  Use this feature in git-gui and get rid of
>> that warning.
>>
>> Tested-by: Johannes Sixt <j6t@kdbg.org>
>> Reviewed-by: Stefan Beller <sbeller@google.com>
>> Signed-off-by: Rene Scharfe <l.s.r@web.de>
>> Signed-off-by: Pat Thoyts <patthoyts@users.sourceforge.net>
>
>OK, but perhaps move me from From: to Original-patch-by: as the
>version check is a big enough change in itself.  Or add a separate
>commit for it.  Or at least mention that you added the check in the
>commit message.
>
>Thanks,
>René

As this is one of the ones already staged to git's 'next' I'll make this as a separate commit on top.

-- 
Pat Thoyts                            http://www.patthoyts.tk/
PGP fingerprint 2C 6E 98 07 2C 59 C8 97  10 CE 11 E6 04 E0 B9 DD
Previous: René Scharfe
Message 7 of 7 in “git-gui: stop using deprecated merge syntax”
  1. git-gui: stop using deprecated merge syntaxRené Scharfe, Sep 24, 2016
  2. Johannes SixtSep 24, 2016
  3. Junio C HamanoSep 25, 2016
  4. Stefan BellerSep 26, 2016
  5. Pat ThoytsOct 3, 2016
  6. René ScharfeOct 3, 2016
  7. Pat ThoytsOct 3, 2016

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.