From: "John J. Franey" <jjfraney@gmail.com>
To: git@vger.kernel.org
Subject: Re: A Visual Git Reference
Date: Wed, 10 Feb 2010 03:40:18 +0000 (UTC) [thread overview]
Message-ID: <hkt9r2$gi8$1@ger.gmane.org> (raw)
In-Reply-To: alpine.LNX.2.00.1002081513430.14365@iabervon.org
On Mon, 08 Feb 2010 16:57:12 -0500, Daniel Barkalow wrote:
> 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
next prev parent reply other threads:[~2010-02-10 4:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 19:34 A Visual Git Reference Mark Lodato
2010-02-08 19:51 ` Peter Baumann
2010-02-08 20:21 ` Mark Lodato
2010-02-08 20:34 ` Jon Seymour
2010-02-08 20:57 ` Mark Lodato
2010-02-09 0:09 ` Johannes Schindelin
2010-02-08 21:57 ` Daniel Barkalow
2010-02-09 0:18 ` Mark Lodato
2010-02-10 3:40 ` John J. Franey [this message]
2010-02-10 5:20 ` Jeff King
2010-03-17 19:03 ` Scott R. Godin
2010-02-10 17:02 ` Dilip M
2010-02-18 1:17 ` Michael Witten
2010-02-18 1:39 ` Jeff King
2010-02-18 1:39 ` Mark Lodato
2010-02-18 3:03 ` Michael Witten
2010-02-18 12:38 ` Tor Arvid Lund
2010-02-18 12:53 ` Tay Ray Chuan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='hkt9r2$gi8$1@ger.gmane.org' \
--to=jjfraney@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).