en-us http://www.gitcasts.com All comments from Welcome to GitCasts Brianhttp://localhost:3004/posts/interactive-adding#IDComment11367401These are great. I actually love the pace that you are going. Tue, 18 Nov 2008 17:53:04 +0000http://localhost:3004/posts/interactive-adding#IDComment11367401 Jayhttp://www.gitcasts.com/posts/railsconf-git-talk#IDComment10715478Very useful video, especially for beginners. Thanks Scott. Fri, 14 Nov 2008 03:41:39 +0000http://www.gitcasts.com/posts/railsconf-git-talk#IDComment10715478 Nissehttp://localhost:3004/posts/interactive-adding#IDComment8913563Super Wed, 22 Oct 2008 00:52:56 +0000http://localhost:3004/posts/interactive-adding#IDComment8913563 Florian Mayerhttp://www.gitcasts.com/posts/branching-and-merging#IDComment8811333Nice! Helped me a lot! Sun, 19 Oct 2008 16:45:13 +0000http://www.gitcasts.com/posts/branching-and-merging#IDComment8811333 Praveenhttp://www.gitcasts.com/posts/branching-and-merging#IDComment8340843It would be great if you could tell us how you get the colors on your terminal(or is it iTerm?). I find the color coding very helpful & I'm unable to get the colors to work on my terminal(Leopard) :( Thanks in advance. Sat, 11 Oct 2008 17:52:01 +0000http://www.gitcasts.com/posts/branching-and-merging#IDComment8340843 Praveenhttp://localhost:3004/posts/interactive-adding#IDComment8339513Great going Scott. Thanks for the screen cast's, love them all. Keep up the good work! Sat, 11 Oct 2008 16:52:01 +0000http://localhost:3004/posts/interactive-adding#IDComment8339513 jithuhttp://www.gitcasts.com/posts/setup-initialization-and-cloning#IDComment6302183great way to start understanding git Mon, 15 Sep 2008 10:57:14 +0000http://www.gitcasts.com/posts/setup-initialization-and-cloning#IDComment6302183 lomakinhttp://www.gitcasts.com/posts/setup-initialization-and-cloning#IDComment6122443Very cool cast for newbies, who don't know what git is. I think, by several words this cast can tell svn-users why git is can be more efficient than svn. Wed, 10 Sep 2008 11:31:41 +0000http://www.gitcasts.com/posts/setup-initialization-and-cloning#IDComment6122443 JWhttp://www.gitcasts.com/posts/setup-initialization-and-cloning#IDComment5923313As I watch you are set up Git, I am wondering what you are using. I see you are using a mac, and I am using a pc right now (can't switch just yet) so would I just use a command line or is there anything better? Any help understanding would be great. :) Thank you... Sun, 7 Sep 2008 19:08:51 +0000http://www.gitcasts.com/posts/setup-initialization-and-cloning#IDComment5923313 Sergheihttp://www.gitcasts.com/posts/git-on-windows#IDComment5663033Very nice and very helpfull video! Thu, 4 Sep 2008 06:12:13 +0000http://www.gitcasts.com/posts/git-on-windows#IDComment5663033 Alex_Coleshttp://www.gitcasts.com/posts/4#IDComment4962983@sensei git --no-pager log Wed, 27 Aug 2008 02:21:04 +0000http://www.gitcasts.com/posts/4#IDComment4962983 senseihttp://www.gitcasts.com/posts/4#IDComment4954503how do I get it to not pipe to less! OMFG! Tue, 26 Aug 2008 20:16:46 +0000http://www.gitcasts.com/posts/4#IDComment4954503 Elliot Larsonhttp://www.gitcasts.com/posts/empty-branches#IDComment4652633It may be philosophically offensive to do an empty commit, however, you can't run the "git branches" command successfully until you do. I guess I'm just antsy. I want to see my nice pretty new empty branch's name printed out on the command line in all its glory before I start working in the directory... it's wrong, I know it's wrong. I found this process a bit onerous, so I created a shell function and alias, which I stuck in my .bash_profile file: function git_empty_branch { git-symbolic-ref HEAD refs/heads/$1 rm .git/index git clean -fdx git commit --allow-empty -m "initial branch commit" } alias geb="git_empty_branch" So you execute it like so: $ git_empty_branch website or $ geb website Thu, 21 Aug 2008 20:45:14 +0000http://www.gitcasts.com/posts/empty-branches#IDComment4652633 Carlhttp://gitcasts.com/posts/git-diff#IDComment4640003Here, here, I agree! These casts are very helpful, and I really wouldn't worry about making something look hard. After all, if all of this really was easy and intuitive, you wouldn't need to do these casts for people. There'd be no one watching them. Tools like git are trying to do something that, while important, is complicated and therefore hard. If it was easy we'd all just do it ourselves, rather than use a tool. What your screencasts do is make it easier for us to understand and use the tools. I agree git 'show' might be useful to do a cast on, but if you had tried to show that in this cast it would have just become more complicated as it doesn't do quite the same thing and probably does deserve its own show. Thu, 21 Aug 2008 12:16:05 +0000http://gitcasts.com/posts/git-diff#IDComment4640003 Henrik Nhttp://gitcasts.com/posts/git-submodules#IDComment4292423Curious to know more about these branch issues as well. Scott, any comment? Fri, 8 Aug 2008 14:16:58 +0000http://gitcasts.com/posts/git-submodules#IDComment4292423 Git Novicehttp://www.gitcasts.com/posts/git-on-windows#IDComment3556973Thanks for posting. It is terrific. But I have a question, if I am using git for windows, instead of using push to GIGHUB, could it be puhsed to Git public repository sitting on Unix via HTTP? Is anywhere I can find such information? Wed, 30 Jul 2008 16:08:25 +0000http://www.gitcasts.com/posts/git-on-windows#IDComment3556973 ctehttp://gitcasts.com/posts/git-diff#IDComment3296003Oopsie, forgot the 'xargs' before the pipe to git show. Here's the command in one line (README is a file in my git repos): git log --pretty=format:%h -n 1 README | xargs git show | grep index | perl -pe '/(w+)..(w+)/; `git show $1 > /tmp/a && git show $2 > /tmp/b`' && vimdiff /tmp/a /tmp/b Not the prettiest thing to look at :) Wed, 23 Jul 2008 03:05:23 +0000http://gitcasts.com/posts/git-diff#IDComment3296003 ctehttp://gitcasts.com/posts/git-diff#IDComment3295793What is the easiest way to achieve a "diff against previous revision" action for a given file? I did something like the following: git log --pretty=format:%h -n 1 README | git show (got the current and previous sha values for the README blob) git show <sha1> > /tmp/a && git show <sha1> > /tmp/b && vimdiff /tmp/a /tmp/b This seems tedious for such a common thing to do... Wed, 23 Jul 2008 02:31:33 +0000http://gitcasts.com/posts/git-diff#IDComment3295793 rbhttp://gitcasts.com/posts/git-diff#IDComment3197651Good point Scott. Keep the good work. Only those who do nothing don't make mistakes.... As to the spellos and silences in the cast: you spend so much time preparing and recording it that I would not dare to complain! I'd rather see you spend your precious time on other casts than editing those already existing. Looking forwad to future gitcasts! Raph Thu, 17 Jul 2008 04:43:21 +0000http://gitcasts.com/posts/git-diff#IDComment3197651 Scott Chaconhttp://gitcasts.com/posts/git-diff#IDComment3142751Well, it will fulfill two goals - teach people what a useful, simple tool does (rev-parse) AND harden the reputation, etc. Yes, 'git show' will resolve the treeish, but it will also spit out all sorts of information I don't want - I didn't want the whole commit diff in that instance, I just wanted the sha. It's not like I'm teaching "what you need to do here is write-tree, then commit-tree..." instead of teaching 'git commit' - I'm showing a simpler tool for the job I'm trying to get done. I personally don't much like 'git show' - it assumes too much for me, I would rather teach people what is happening so they understand what git does. I do not think it is complicating, I _hope_ it is instructive of what git does, rather than gloss over it. I would rather teach 4 specific, directed tools, even if you consider them scary for mere mortals, than gloss over it with a tool I personally rarely use. People are generally pretty smart and are not going to throw up their hands because of something like that - especially if they are investing time in watching this videocast series. As to the email, I am not replying to you for your benefit, but so that people understand that I don't agree with you. If you wish to keep track of the conversation, there are several comment feeds on the page you can subscribe to. Lastly, just as advice for you - your feedback would probably be much better responded to if you were not so combative and arrogant about it. I will consider your opinion and will likely do a cast on 'git show' at some point in the near future because I think you overall have some good points, but my instinct is now to _not_ do it just to spite you. Be kind, my friend, we're all on the same side here. Wed, 16 Jul 2008 12:02:14 +0000http://gitcasts.com/posts/git-diff#IDComment3142751