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

Re: A Visual Git Reference

From
JFJohn J. Franey <jjfraney@gmail.com>
Date
Feb 10, 2010, 03:40 UTC
Message-ID
<hkt9r2$gi8$1@ger.gmane.org>
In-Reply-To
<alpine.LNX.2.00.1002081513430.14365@iabervon.org>
On Mon, 08 Feb 2010 16:57:12 -0500, Daniel Barkalow wrote:
Show 26 quoted lines
> On Mon, 8 Feb 2010, Mark Lodato wrote:
> 
>> All,
>> 
>> I put together a "Visual Git Reference" containing visualizations of
>> the most common git commands, for people who prefer to see images over
>> text.  It is designed as a reference, not a tutorial, so readers need
>> to have some amount of experience before the page will become useful.
>> 
>> URL: http://marklodato.github.com/visual-git-guide/ Git repo:
>> http://github.com/marklodato/visual-git-guide/
>> 
>> If you have any feedback or suggestions, please let me know!
> 
> The "3-way merge" node should graphically distinguish the base from the
> two sides, rather than having all three just go in. The "3-way merge"
> operation is tricky to understand visually without some sort of "split
> and rejoin, with specific points" thing.
> 
> Also, it would probably be worth showing the use of the index in the
> process of a 3-way merge: all three versions go into the blue box, and a
> combination (with conflict markers) goes into the pink box; the user
> cleans up the pink box, and replaces the 3-part blue box content with
> the cleaned-up single result content; then the commit gives the diagram
> you have for "git merge other".
> 

I often have difficulty trying to internally visualize a mapping from the commits of a merge to the panes of a kdiff3 session. I have special difficulty keeping straight which commit is the LOCAL and which is the REMOTE. Looking at your visual guide, I can almost see a kdiff session in this section on three way merge where each commit sits in one of the panes. b325c in upper left, ed489 in upper middle, and 33104 in upper right, "Working Directory" on the bottom pane. Not sure if that graphic would be useful to anyone else. Thought I'd throw it in for grins.

I learned a few things from your guide. I've been using git for about a year and a half. Thanks.

John
Previous: Mark LodatoNext: Jeff King
Message 9 of 18 in “A Visual Git Reference”
  1. Mark LodatoFeb 8, 2010
  2. Peter BaumannFeb 8, 2010
  3. Mark LodatoFeb 8, 2010
  4. Jon SeymourFeb 8, 2010
  5. Mark LodatoFeb 8, 2010
  6. Johannes SchindelinFeb 9, 2010
  7. Daniel BarkalowFeb 8, 2010
  8. Mark LodatoFeb 9, 2010
  9. John J. FraneyFeb 10, 2010
  10. Jeff KingFeb 10, 2010
  11. Scott R. GodinMar 17, 2010
  12. Dilip MFeb 10, 2010
  13. Michael WittenFeb 18, 2010
  14. Jeff KingFeb 18, 2010
  15. Mark LodatoFeb 18, 2010
  16. Michael WittenFeb 18, 2010
  17. Tor Arvid LundFeb 18, 2010
  18. Tay Ray ChuanFeb 18, 2010

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.