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

Re: Git terminology

From
SPSébastien Pierre <sebastien@xprima.com>
Date
Mar 29, 2006, 16:11 UTC
Message-ID
<20060329111112.55bb8d44.sebastien@xprima.com>
In-Reply-To
<7vodzp9r8r.fsf@assigned-by-dhcp.cox.net>
On Wed, 29 Mar 2006 07:59:16 -0800
Junio C Hamano <junkio@cox.net> wrote:
 
Show 18 quoted lines
> Probably we can just say "ref" where we say "refname".
> 
> A fast-forward is where you have a revision and you are
> "merging" other's change that happen to be a descendant what you
> have.  In such a case, you do not make a new merge commit but
> just update to his revision.  That is:
> 
>           o---o---o---o his               o---o---o---o his
>          /                      ->       /             \
>     o---o---o---o yours             o---o---o---o-------* yours
> 
> updating to his needs a merge like above, but in this case:
> 
>           o---o---o---o his               o---o---o---o his = yours
>          /                      ->       /
>     o---o yours                     o---o
> 
> you just update to his.
Ah, ok. The diagrams are really helpful to get what "fast forward" is.
Thanks !
 -- Sébastien
Previous: Junio C Hamano
Message 4 of 4 in “Git terminology”
  1. Sébastien PierreMar 29, 2006
  2. J. Bruce FieldsMar 29, 2006
  3. Junio C HamanoMar 29, 2006
  4. Sébastien PierreMar 29, 2006

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.