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

Re: [PATCH] git-merge-ff: fast-forward only merge

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jun 28, 2007, 13:01 UTC
Message-ID
<Pine.LNX.4.64.0706281400530.4438@racer.site>
In-Reply-To
<20070628113346.GA4914@moooo.ath.cx>
Hi,
On Thu, 28 Jun 2007, Matthias Lederhofer wrote:
Show 24 quoted lines
> Sam Vilain <sam.vilain@catalyst.net.nz> wrote:
> > This is primarily so that there is an easy switch to 'git-pull' to
> > be sure to fast forward only.
> > ---
> >  Documentation/merge-strategies.txt |    5 +++++
> >  Makefile                           |    2 +-
> >  git-merge-ff.sh                    |    8 ++++++++
> >  3 files changed, 14 insertions(+), 1 deletions(-)
> >  create mode 100644 git-merge-ff.sh
> 
> git-merge-ff.sh should be executable, added to .gitignore and the
> strategy should be added to the available strategies.
> 
> And somehow it did not work for me at all:
> 
> % git merge -s ff origin/master
> git-merge.sh: needs update   
> Trying really trivial in-index merge...
> Wonderful.
> In-index merge
> [..]
> % git show HEAD|grep Merge
> Merge: 117a93c... f578825...
>     Merge commit 'origin/master'

To prevent something like this to happen, may I suggest adding a really simple, small test case?

Ciao, Dscho

Previous: Matthias Lederhofer
Message 3 of 3 in “git-merge-ff: fast-forward only merge”
  1. git-merge-ff: fast-forward only mergeSam Vilain, Jun 26, 2007
  2. Matthias LederhoferJun 28, 2007
  3. Johannes SchindelinJun 28, 2007

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.