{"thread":{"id":"22573","subject":"A Visual Git Reference","startedAt":"2010-02-08T19:34:21Z","lastAt":"2010-03-17T19:03:11Z","messageCount":18,"participants":["Mark Lodato","Peter Baumann","Jon Seymour","Daniel Barkalow","Johannes Schindelin","John J. Franey","Jeff King","Dilip M","Michael Witten","Tor Arvid Lund","Tay Ray Chuan","Scott R. Godin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"133940","messageId":"ca433831002081134m698f531bwa22f0474db0cdcb@mail.gmail.com","threadId":"22573","inReplyTo":null,"subject":"A Visual Git Reference","fromName":"Mark Lodato","fromEmail":"lodatom@gmail.com","sentAt":"2010-02-08T19:34:21Z","receivedAt":"2010-02-08T19:34:21Z","isPatch":false,"sender":{"key":"lodatom@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58860?v=4"},"body":"All,\n\nI put together a \"Visual Git Reference\" containing visualizations of\nthe most common git commands, for people who prefer to see images over\ntext. It is designed as a reference, not a tutorial, so readers need\nto have some amount of experience before the page will become useful.\n\nURL: http://marklodato.github.com/visual-git-guide/\nGit repo: http://github.com/marklodato/visual-git-guide/\n\nIf you have any feedback or suggestions, please let me know!\n\nCheers,\nMark\n"},{"id":"133941","messageId":"20100208195141.GF30877@m62s10.vlinux.de","threadId":"22573","inReplyTo":"ca433831002081134m698f531bwa22f0474db0cdcb@mail.gmail.com","subject":"Re: A Visual Git Reference","fromName":"Peter Baumann","fromEmail":"waste.manager@gmx.de","sentAt":"2010-02-08T19:51:41Z","receivedAt":"2010-02-08T19:51:41Z","isPatch":false,"sender":{"key":"waste.manager@gmx.de","avatar":null},"body":"On Mon, Feb 08, 2010 at 02:34:21PM -0500, Mark Lodato wrote:\n> All,\n> \n> I put together a \"Visual Git Reference\" containing visualizations of\n> the most common git commands, for people who prefer to see images over\n> text. It is designed as a reference, not a tutorial, so readers need\n> to have some amount of experience before the page will become useful.\n> \n> URL: http://marklodato.github.com/visual-git-guide/\n> Git repo: http://github.com/marklodato/visual-git-guide/\n> \n> If you have any feedback or suggestions, please let me know!\n\nI have only glanced over the page, but it seems you have made the time\nflow from right to left. Is this intentional? I find it not very intuitive.\n"},{"id":"133944","messageId":"ca433831002081221o660ff882o703381c5f066512e@mail.gmail.com","threadId":"22573","inReplyTo":"20100208195141.GF30877@m62s10.vlinux.de","subject":"Re: A Visual Git Reference","fromName":"Mark Lodato","fromEmail":"lodatom@gmail.com","sentAt":"2010-02-08T20:21:38Z","receivedAt":"2010-02-08T20:21:38Z","isPatch":false,"sender":{"key":"lodatom@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58860?v=4"},"body":"On Mon, Feb 8, 2010 at 2:51 PM, Peter Baumann wrote:\n> I have only glanced over the page, but it seems you have made the time\n> flow from right to left. Is this intentional? I find it not very intuitive.\n\nGood call. I don't know why I did that. I just pushed a new version\nthat goes left-to-right.\n\nThanks,\nMark\n"},{"id":"133948","messageId":"2cfc40321002081234t2e8585bxfbcae41b18804e70@mail.gmail.com","threadId":"22573","inReplyTo":"ca433831002081221o660ff882o703381c5f066512e@mail.gmail.com","subject":"Re: A Visual Git Reference","fromName":"Jon Seymour","fromEmail":"jon.seymour@gmail.com","sentAt":"2010-02-08T20:34:53Z","receivedAt":"2010-02-08T20:34:53Z","isPatch":false,"sender":{"key":"jon.seymour@gmail.com","avatar":"https://avatars.githubusercontent.com/u/207131?v=4"},"body":"G'day Mark,\n\nNice diagrams. You might want to change the arrows on the diffs to be\nconsistently in direction of the forward diff.\n\njon.\n\nOn Tue, Feb 9, 2010 at 7:21 AM, Mark Lodato wrote:\n> On Mon, Feb 8, 2010 at 2:51 PM, Peter Baumann wrote:\n>> I have only glanced over the page, but it seems you have made the time\n>> flow from right to left. Is this intentional? I find it not very intuitive.\n>\n> Good call.  I don't know why I did that.  I just pushed a new version\n> that goes left-to-right.\n>\n> Thanks,\n> Mark\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n>\n"},{"id":"133951","messageId":"ca433831002081257u4fec4010sa382f1e1bfeb4c0b@mail.gmail.com","threadId":"22573","inReplyTo":"2cfc40321002081234t2e8585bxfbcae41b18804e70@mail.gmail.com","subject":"Re: A Visual Git Reference","fromName":"Mark Lodato","fromEmail":"lodatom@gmail.com","sentAt":"2010-02-08T20:57:25Z","receivedAt":"2010-02-08T20:57:25Z","isPatch":false,"sender":{"key":"lodatom@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58860?v=4"},"body":"On Mon, Feb 8, 2010 at 3:34 PM, Jon Seymour wrote:\n> Nice diagrams. You might want to change the arrows on the diffs to be\n> consistently in direction of the forward diff.\n\nThanks. You're right, the da985->b325c was the only one that made\nsense - the rest were reversed. Is this what you meant? I just\npushed this change, so it should be fixed.\n\nMark\n"},{"id":"133957","messageId":"alpine.LNX.2.00.1002081513430.14365@iabervon.org","threadId":"22573","inReplyTo":"ca433831002081134m698f531bwa22f0474db0cdcb@mail.gmail.com","subject":"Re: A Visual Git Reference","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2010-02-08T21:57:12Z","receivedAt":"2010-02-08T21:57:12Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"On Mon, 8 Feb 2010, Mark Lodato wrote:\n\n> All,\n> \n> I put together a \"Visual Git Reference\" containing visualizations of\n> the most common git commands, for people who prefer to see images over\n> text. It is designed as a reference, not a tutorial, so readers need\n> to have some amount of experience before the page will become useful.\n> \n> URL: http://marklodato.github.com/visual-git-guide/\n> Git repo: http://github.com/marklodato/visual-git-guide/\n> \n> If you have any feedback or suggestions, please let me know!\n\nThe \"3-way merge\" node should graphically distinguish the base from the \ntwo sides, rather than having all three just go in. The \"3-way merge\" \noperation is tricky to understand visually without some sort of \"split and \nrejoin, with specific points\" thing.\n\nAlso, it would probably be worth showing the use of the index in the \nprocess of a 3-way merge: all three versions go into the blue box, and a \ncombination (with conflict markers) goes into the pink box; the user \ncleans up the pink box, and replaces the 3-part blue box content with the \ncleaned-up single result content; then the commit gives the diagram you \nhave for \"git merge other\".\n\nI think you should introduce the detached HEAD situation early; right \nafter \"git checkout HEAD~ files\", it would be worth showing \"git checkout \nHEAD~\". It's pretty common for people in the \"technical user\" part of the \nkernel community to use git to browse history and test different commits, \nand never do a commit at all. This is a pretty common mode across many \nversion control systems (e.g., \"cvs checkout -D yesterday\"), and nothing \nunexpected happens if you don't try to commit while doing it. In fact, you \ncould show tracking down a bug introduced between maint and master by \nchecking out c10b9 and then da985.\n\nThen, later, you can bring up the fact that you can actually do commits in \nthat situation, and show how that works. That part is the part that's \nnovel and could potentially lead to people doing work and having it become \nunreachable. Also, after commiting with a detached HEAD, the normal next \nstep is to create a new branch (\"git checkout -b new-topic\").\n\n\t-Daniel\n*This .sig left intentionally blank*\n"},{"id":"133970","messageId":"alpine.DEB.1.00.1002090109100.4985@pacific.mpi-cbg.de","threadId":"22573","inReplyTo":"ca433831002081221o660ff882o703381c5f066512e@mail.gmail.com","subject":"Re: A Visual Git Reference","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2010-02-09T00:09:35Z","receivedAt":"2010-02-09T00:09:35Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nto save you time: I added a link to the Git Wiki.\n\nCiao,\nDscho\n"},{"id":"133971","messageId":"ca433831002081618s1e3193c3ge7b637ede540533a@mail.gmail.com","threadId":"22573","inReplyTo":"alpine.LNX.2.00.1002081513430.14365@iabervon.org","subject":"Re: A Visual Git Reference","fromName":"Mark Lodato","fromEmail":"lodatom@gmail.com","sentAt":"2010-02-09T00:18:14Z","receivedAt":"2010-02-09T00:18:14Z","isPatch":false,"sender":{"key":"lodatom@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58860?v=4"},"body":"On Mon, Feb 8, 2010 at 4:57 PM, Daniel Barkalow wrote:\n> The \"3-way merge\" node should graphically distinguish the base from the\n> two sides, rather than having all three just go in. The \"3-way merge\"\n> operation is tricky to understand visually without some sort of \"split and\n> rejoin, with specific points\" thing.\n\nYes, I'm not happy with the merge picture at all. As you said, it's\ndifficult to draw a nice picture for it that doesn't become too\ncomplex. I'll have to think of a better way...\n\n> Also, it would probably be worth showing the use of the index in the\n> process of a 3-way merge: all three versions go into the blue box, and a\n> combination (with conflict markers) goes into the pink box; the user\n> cleans up the pink box, and replaces the 3-part blue box content with the\n> cleaned-up single result content; then the commit gives the diagram you\n> have for \"git merge other\".\n\nMy fear is making the graphic too complicated. That said, it may be\nworth making separate graphics: a simple no-conflict case, and a more\ncomplicated conflict case.\n\n> I think you should introduce the detached HEAD situation early; right\n> after \"git checkout HEAD~ files\", it would be worth showing \"git checkout\n> HEAD~\". It's pretty common for people in the \"technical user\" part of the\n> kernel community to use git to browse history and test different commits,\n> and never do a commit at all. This is a pretty common mode across many\n> version control systems (e.g., \"cvs checkout -D yesterday\"), and nothing\n> unexpected happens if you don't try to commit while doing it.\n\nGood point. At your suggestion, I moved up the detached HEAD section\nand integrated part of it into the checkout section. You're right,\nthis does come up a lot, so I should cover it.\n\n> In fact, you\n> could show tracking down a bug introduced between maint and master by\n> checking out c10b9 and then da985.\n\nI may add a section on git bisect in the future.\n\n> Then, later, you can bring up the fact that you can actually do commits in\n> that situation, and show how that works. That part is the part that's\n> novel and could potentially lead to people doing work and having it become\n> unreachable. Also, after commiting with a detached HEAD, the normal next\n> step is to create a new branch (\"git checkout -b new-topic\").\n\nDone. Good idea.\n\nThanks for the feedback. If you have any other thoughts, I'd be glad\nto hear them!\nMark\n"},{"id":"134113","messageId":"hkt9r2$gi8$1@ger.gmane.org","threadId":"22573","inReplyTo":"alpine.LNX.2.00.1002081513430.14365@iabervon.org","subject":"Re: A Visual Git Reference","fromName":"John J. Franey","fromEmail":"jjfraney@gmail.com","sentAt":"2010-02-10T03:40:18Z","receivedAt":"2010-02-10T03:40:18Z","isPatch":false,"sender":{"key":"jjfraney@gmail.com","avatar":null},"body":"On Mon, 08 Feb 2010 16:57:12 -0500, Daniel Barkalow wrote:\n\n> On Mon, 8 Feb 2010, Mark Lodato wrote:\n> \n>> All,\n>> \n>> I put together a \"Visual Git Reference\" containing visualizations of\n>> the most common git commands, for people who prefer to see images over\n>> text. It is designed as a reference, not a tutorial, so readers need\n>> to have some amount of experience before the page will become useful.\n>> \n>> URL: http://marklodato.github.com/visual-git-guide/ Git repo:\n>> http://github.com/marklodato/visual-git-guide/\n>> \n>> If you have any feedback or suggestions, please let me know!\n> \n> The \"3-way merge\" node should graphically distinguish the base from the\n> two sides, rather than having all three just go in. The \"3-way merge\"\n> operation is tricky to understand visually without some sort of \"split\n> and rejoin, with specific points\" thing.\n> \n> Also, it would probably be worth showing the use of the index in the\n> process of a 3-way merge: all three versions go into the blue box, and a\n> combination (with conflict markers) goes into the pink box; the user\n> cleans up the pink box, and replaces the 3-part blue box content with\n> the cleaned-up single result content; then the commit gives the diagram\n> you have for \"git merge other\".\n> \n\nI often have difficulty trying to internally visualize a mapping from the \ncommits of a merge to the panes of a kdiff3 session. I have special \ndifficulty keeping straight which commit is the LOCAL and which is the \nREMOTE. Looking at your visual guide, I can almost see a kdiff session \nin this section on three way merge where each commit sits in one of the \npanes. b325c in upper left, ed489 in upper middle, and 33104 in upper \nright, \"Working Directory\" on the bottom pane. Not sure if that graphic \nwould be useful to anyone else. Thought I'd throw it in for grins.\n\nI learned a few things from your guide. I've been using git for about a \nyear and a half. Thanks.\n\nJohn\n"},{"id":"134120","messageId":"20100210052057.GE28526@coredump.intra.peff.net","threadId":"22573","inReplyTo":"ca433831002081134m698f531bwa22f0474db0cdcb@mail.gmail.com","subject":"Re: A Visual Git Reference","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2010-02-10T05:20:57Z","receivedAt":"2010-02-10T05:20:57Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Feb 08, 2010 at 02:34:21PM -0500, Mark Lodato wrote:\n\n> I put together a \"Visual Git Reference\" containing visualizations of\n> the most common git commands, for people who prefer to see images over\n> text. It is designed as a reference, not a tutorial, so readers need\n> to have some amount of experience before the page will become useful.\n> \n> URL: http://marklodato.github.com/visual-git-guide/\n> Git repo: http://github.com/marklodato/visual-git-guide/\n> \n> If you have any feedback or suggestions, please let me know!\n\nThis looks really awesome, thanks for doing it (though I'll admit I\nthrew up in my mouth a little when I saw you did all of the diagrams as\nTeX. ;) ).\n\nOne of the projects I have wanted to do but never found time for is a\n\"Git Picture Glossary\". I was intending to start with much simpler\nconcepts, like how the various object types relate, what a ref is, how a\nsymref differs, what a detached HEAD is, etc. And then move on to \"here\nis what happens when you branch\", \"here is what happens when you merge\",\netc. Sort of like \"Git for Computer Scientists\", but organized as a\nglossary, with each entry starting off with \"to understand this, you\nfirst need to understand entries X and Y\", with links.\n\nAnd it seems like what you have done is more or less the same thing,\nexcept you skipped all of the really basic entries and went straight to\nthe action-oriented ones.\n\n-Peff\n"},{"id":"134152","messageId":"c94f8e121002100902k2203ebcave7c4050cbf5000cd@mail.gmail.com","threadId":"22573","inReplyTo":"ca433831002081134m698f531bwa22f0474db0cdcb@mail.gmail.com","subject":"Re: A Visual Git Reference","fromName":"Dilip M","fromEmail":"dilipm79@gmail.com","sentAt":"2010-02-10T17:02:59Z","receivedAt":"2010-02-10T17:02:59Z","isPatch":false,"sender":{"key":"dilipm79@gmail.com","avatar":"https://gravatar.com/avatar/9417e308513ce9251de2802a026c72eb164e6c9b9d7143a3ee13f6ed0c4d1bd5?d=mp&s=160"},"body":"Hello Mark,\n\n\nOn Tue, Feb 9, 2010 at 1:04 AM, Mark Lodato wrote:\n> All,\n>\n> I put together a \"Visual Git Reference\" containing visualizations of\n> the most common git commands, for people who prefer to see images over\n> text.  It is designed as a reference, not a tutorial, so readers need\n> to have some amount of experience before the page will become useful.\n>\n> URL: http://marklodato.github.com/visual-git-guide/\n> Git repo: http://github.com/marklodato/visual-git-guide/\n>\n> If you have any feedback or suggestions, please let me know!\n\nThis is very helpful for git users...:) Thanks...\n\n\n-- \nDilip\n\nEveryone is gifted - but some people never open their package!\n"},{"id":"134906","messageId":"b4087cc51002171717i3a8052a9jbf8c59b4975c0e1c@mail.gmail.com","threadId":"22573","inReplyTo":"ca433831002081134m698f531bwa22f0474db0cdcb@mail.gmail.com","subject":"Re: A Visual Git Reference","fromName":"Michael Witten","fromEmail":"mfwitten@gmail.com","sentAt":"2010-02-18T01:17:20Z","receivedAt":"2010-02-18T01:17:20Z","isPatch":false,"sender":{"key":"mfwitten@gmail.com","avatar":"https://avatars.githubusercontent.com/u/597101?v=4"},"body":"On Mon, Feb 8, 2010 at 1:34 PM, Mark Lodato wrote:\n> All,\n>\n> I put together a \"Visual Git Reference\" containing visualizations of\n> the most common git commands, for people who prefer to see images over\n> text.\n\nIt would be great if you could output either larger images or\nsomething that is resolution-independent like SVG.\n"},{"id":"134910","messageId":"20100218013943.GC15870@coredump.intra.peff.net","threadId":"22573","inReplyTo":"b4087cc51002171717i3a8052a9jbf8c59b4975c0e1c@mail.gmail.com","subject":"Re: A Visual Git Reference","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2010-02-18T01:39:43Z","receivedAt":"2010-02-18T01:39:43Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Feb 17, 2010 at 07:17:20PM -0600, Michael Witten wrote:\n\n> On Mon, Feb 8, 2010 at 1:34 PM, Mark Lodato wrote:\n> > All,\n> >\n> > I put together a \"Visual Git Reference\" containing visualizations of\n> > the most common git commands, for people who prefer to see images over\n> > text.\n> \n> It would be great if you could output either larger images or\n> something that is resolution-independent like SVG.\n\nTry\n\n http://marklodato.github.com/visual-git-guide/index-svg.html\n\n-Peff\n"},{"id":"134912","messageId":"ca433831002171739h7ae0de63hfdaa05841fbd388c@mail.gmail.com","threadId":"22573","inReplyTo":"b4087cc51002171717i3a8052a9jbf8c59b4975c0e1c@mail.gmail.com","subject":"Re: A Visual Git Reference","fromName":"Mark Lodato","fromEmail":"lodatom@gmail.com","sentAt":"2010-02-18T01:39:43Z","receivedAt":"2010-02-18T01:39:43Z","isPatch":false,"sender":{"key":"lodatom@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58860?v=4"},"body":"The first paragraph has a link to an SVG version of the page. It's\nnot the default since SVG support varies greatly between browsers.\nStill, I'll consider making the images bigger.\n\nThanks,\nMark\n\nOn Wed, Feb 17, 2010 at 8:17 PM, Michael Witten wrote:\n> On Mon, Feb 8, 2010 at 1:34 PM, Mark Lodato wrote:\n>> All,\n>>\n>> I put together a \"Visual Git Reference\" containing visualizations of\n>> the most common git commands, for people who prefer to see images over\n>> text.\n>\n> It would be great if you could output either larger images or\n> something that is resolution-independent like SVG.\n>\n"},{"id":"134922","messageId":"b4087cc51002171903r3689f59eue4ab68d8d939d8bc@mail.gmail.com","threadId":"22573","inReplyTo":"ca433831002171739h7ae0de63hfdaa05841fbd388c@mail.gmail.com","subject":"Re: A Visual Git Reference","fromName":"Michael Witten","fromEmail":"mfwitten@gmail.com","sentAt":"2010-02-18T03:03:12Z","receivedAt":"2010-02-18T03:03:12Z","isPatch":false,"sender":{"key":"mfwitten@gmail.com","avatar":"https://avatars.githubusercontent.com/u/597101?v=4"},"body":"On Wed, Feb 17, 2010 at 7:39 PM, Jeff King wrote:\n> Try\n>\n> http://marklodato.github.com/visual-git-guide/index-svg.html\n\nOn Wed, Feb 17, 2010 at 7:39 PM, Mark Lodato wrote:\n> The first paragraph has a link to an SVG version of the page.  It's\n> not the default since SVG support varies greatly between browsers.\n\nOh... :-D\n"},{"id":"134963","messageId":"1a6be5fa1002180438i4241321ducde5b0b03de3b563@mail.gmail.com","threadId":"22573","inReplyTo":"ca433831002171739h7ae0de63hfdaa05841fbd388c@mail.gmail.com","subject":"Re: A Visual Git Reference","fromName":"Tor Arvid Lund","fromEmail":"torarvid@gmail.com","sentAt":"2010-02-18T12:38:32Z","receivedAt":"2010-02-18T12:38:32Z","isPatch":false,"sender":{"key":"torarvid@gmail.com","avatar":"https://avatars.githubusercontent.com/u/439758?v=4"},"body":"On Thu, Feb 18, 2010 at 2:39 AM, Mark Lodato wrote:\n> The first paragraph has a link to an SVG version of the page.  It's\n> not the default since SVG support varies greatly between browsers.\n\nYes, it does :-)\n\nFor me (using Chrome 4 on windows), the SVG images are scaled a little\ntoo big for the box that they are placed in, so the bottom and right\nside is cropped.\n"},{"id":"134965","messageId":"be6fef0d1002180453j7fa6b663nf4619bcee0c6a185@mail.gmail.com","threadId":"22573","inReplyTo":"ca433831002171739h7ae0de63hfdaa05841fbd388c@mail.gmail.com","subject":"Re: A Visual Git Reference","fromName":"Tay Ray Chuan","fromEmail":"rctay89@gmail.com","sentAt":"2010-02-18T12:53:03Z","receivedAt":"2010-02-18T12:53:03Z","isPatch":false,"sender":{"key":"rctay89@gmail.com","avatar":"https://avatars.githubusercontent.com/u/61553?v=4"},"body":"Hi,\n\nOn Thu, Feb 18, 2010 at 9:39 AM, Mark Lodato wrote:\n> The first paragraph has a link to an SVG version of the page.  It's\n> not the default since SVG support varies greatly between browsers.\n\nChrome 4 gives some parsing errors for the SVG files.\n\n Error: Problem parsing d=\"\"\n\nFor example, line 5 of conventions.svg.\n\n-- \nCheers,\nRay Chuan\n"},{"id":"137052","messageId":"hnr91f$rph$1@dough.gmane.org","threadId":"22573","inReplyTo":"20100210052057.GE28526@coredump.intra.peff.net","subject":"Re: A Visual Git Reference","fromName":"Scott R. Godin","fromEmail":"scottg.wp-hackers@mhg2.com","sentAt":"2010-03-17T19:03:11Z","receivedAt":"2010-03-17T19:03:11Z","isPatch":false,"sender":{"key":"scottg.wp-hackers@mhg2.com","avatar":"https://gravatar.com/avatar/766980733f46a32860153479ca94372e4fff5c4632e8586dbbfb143051d231ce?d=mp&s=160"},"body":"On 02/10/2010 12:20 AM, Jeff King wrote:\n> On Mon, Feb 08, 2010 at 02:34:21PM -0500, Mark Lodato wrote:\n>\n>> I put together a \"Visual Git Reference\" containing visualizations of\n>> the most common git commands, for people who prefer to see images over\n>> text. It is designed as a reference, not a tutorial, so readers need\n>> to have some amount of experience before the page will become useful.\n>>\n>> URL: http://marklodato.github.com/visual-git-guide/\n>> Git repo: http://github.com/marklodato/visual-git-guide/\n>>\n>> If you have any feedback or suggestions, please let me know!\n>\n> This looks really awesome, thanks for doing it (though I'll admit I\n> threw up in my mouth a little when I saw you did all of the diagrams as\n> TeX. ;) ).\n\n*chuckle* on the otherhand I was quite intrigued to find out that TeX \nwas used to create all the graphics; especially after seeing all the \nexamples at http://www.texample.net/tikz/examples/all/date/\n\n(BTW great work on the guide, too, even if I am chiming in a bit late to \nthis. still catching up to the news posts I'm behind on. augh.)\n\n-- \n(please respond to the list as opposed to my email box directly,\nunless you are supplying private information you don't want public\non the list)\n"}]}