From: Shakthi Kannan Date: Fri, 05 Jun 2009 04:52:31 GMT Subject: Re: di-git-ally managing love letters - a Git presentation Message-ID: In-Reply-To: Hi, Firstly, thanks for your reply! This is the feedback I was hoping to hear. My replies below: --- On Thu, Jun 4, 2009 at 8:21 PM, Jakub Narebski wrote: | Why don't you use git to manage LaTeX sources, using for example one | of free git hosting sites (repo.or.cz, GitHub, Gitorious)? \-- Practice what you preach :) Sure, could. Will look into it. --- | A few comments: |  * For which git version do you write your presentation? \-- On Fedora 10, git 1.6.0.6. --- | Modern |   git (which might mean just released version, and perhaps even |   yet-to-be-released version) has: |     - git log --oneline == git log --pretty=oneline --abbrev-commit \-- Will remember that. --- |  * Nitpick: git index (also known as staging area) does not contain |   objects itself.  They are put in objects database.  The index |   contains references to those objects (so they can be found). \-- I can mention it as "object ref" or "object(s) ref". --- |  * Suggestion: When showing "git diff", "git diff --cached" and |   "git diff HEAD" output you might want to show which parts |   in the diagram below you compare. \-- Will do. --- |  * Why there is no diagram / graph for tagging? \-- Will do. I guess it should be a tag symbol pointing to the recent commit? --- |  * Nitpick: you have spelled 'git-format-patch' by mistake |   instead of modern 'git format-patch'. \-- Ohh! In git 1.6.0.6, I had git-format-patch. I will keep up with the modern git releases. --- |  * I would personally use "git rm -f ", but it might be easier |   tu add '-f' at the end of line. \-- Will change it. --- |  * I would guess that this usage ("git reset HEAD ") is quite |   rare, \-- I see. I just used it to show it because git printed it in the output, and someone new to using git should know as to what the output meant. --- |  * I think that actual usage of "git reset --soft" is pretty pretty |   rare since we have "git commit --amend". \-- Ohh! I just mentioned it to show the difference between --soft and --hard. --- | I don't know if presentation is not too long. On the other hand it | doesn't cover situations such as non fast-formard merge... \-- Yes. I don't yet have many use-cases, but, I guess it is a reasonable start. Will work on these use cases. Thanks again! SK -- Shakthi Kannan http://www.shakthimaan.com