Git Screencast ?

I am a new user of git and SCMs in general , I have learned a lot from the docs , irc and just using it , but there are just some concepts that hare hard to grasp , I am a very visual persion (probably like a lot of you :) ) , is there a screencast of git somewhere (for free) that can demonstrate some of the advanced features of git... (Also...I have seen both Randal (Schwartz) and Linus' (you better know his last name) presentations at google on git , in which they explain the ideas behind git more than the actual usage,

Thanks

---Mike Donaghy----------- ---Mike@mikedonaghy.org--- ---http://mikedonaghy.org-

On 21/11/07 08:02, Michael Donaghy wrote:

Hi Michael,

what helped me was a) looking at the directory structure under .git b) reading the git user-manual c) http://eagain.net/articles/git-for-computer-scientists/

Especially c) created a big aha-effect. If you really read all the text you should have understood most of it. And hey, since you're a visual person: there are images too! ;)

Greetings, Jojo

On Wednesday 21 November 2007, Michael Donaghy wrote:

There's a company called PeepCode that apparently sell a Git screencast, but I have no idea if it demonstrates advanced features, or just do the basics.

There seems to be a TOC on their website, so you can check that to see if contains what you need:

http://peepcode.com/products/git

Have fun!

...Johan

Michael> I am a new user of git and SCMs in general , I have learned a lot Michael> from the docs , irc and just using it , but there are just some Michael> concepts that hare hard to grasp , I am a very visual persion Michael> (probably like a lot of you :) ) , is there a screencast of git Michael> somewhere (for free) that can demonstrate some of the advanced Michael> features of git... (Also...I have seen both Randal (Schwartz) and Michael> Linus' (you better know his last name) presentations at google on git Michael> , in which they explain the ideas behind git more than the actual Michael> usage,

Having been involved in that screencast that you reference, I'm curious about what you think you're missing in order to use git. The feedback will help me produce better presentations.

John Herland Said:
 > There's a company called PeepCode that apparently sell a Git
 > screencast, but
 > I have no idea if it demonstrates advanced features, or just do the
 > basics.
 >
 > There seems to be a TOC on their website, so you can check that to 
see > if
 > contains what you need:
 >
 > http://peepcode.com/products/git
 >
 >
 > Have fun!

Peepcode has some really good quality screen casts ,yes, but they are for pay , $10 per screen cast and my original message said

 >> "..is there a screencast of git somewhere (for free) that can
 >> demonstrate some of the advanced features of git..."

Also thanks Johannes for that link , I will tak e a look at that

and Randal... you are *EVERYWHERE* ... how do you do that ... , keep up the good work =) (see you in the irc --Ekim)

Michael Donaghy wrote:

The thing that helped me and my co-workers the most was running through the steps of the tutorial, but stopping every time something wasn't absolutely crystal clear and doing gitk or qgit (I prefer qgit, since it seems to display things more consistently and also loads faster).

That primarily helped us get branches under control. We came from a CVS world and never had any branches, as none of us had time or energy to figure out how to merge them back together using those crippled scm's.

I noticed Johannes Gilger already sent you the link to git-for-scientists thing which is also a really good aid, especially when you've read the tutorial and some of the less tech-oriented docs.

Andreas Ericsson wrote:

Yes thank you , although a screen cast would still be ideal , the documentation is very good, also , what do you think of git-gui ? , I think it is the best one

Michael Donaghy wrote:

I don't use it. Partly because I tested it out when it was far from ready and am still somewhat traumatized by the experience, and partly because I'm very comfortable with the command-line tools and have found a workflow that works nicely for me.

On 22/11/07 20:47, Michael Donaghy wrote:

Hi Michael,

I think you're trying to hide the complexity of git. The problem with graphical tools is that they hide complexity from the user, which in some cases is only possibly/good if the user has understood the underlying principles already. Also I think that there are many things which can be done much quicker using a command-line than any gui (as all of the people here will agree). Git is not Time-Machine (this thing from Apple). It is also no good idea to try to view git from a svn's point of view, or try to compare commands. It took me a while to get over that and accept that git is different. I was frustated (and still am sometimes) but i finally understood the whole concept.

About screencasts: I haven't watched that many screencasts in general, but I can hardly imagine that they are better way of teaching things than reading a manual. Watching someone type in commands, hitting "Pause", then trying it myself doesn't seem more intuitive to me than just reading a manual and typing the commands given in regular intervals. Maybe someone can enlighten me about the use of screencasts (in a command-line environment).

Greetings, Jojo

Johannes Gilger <heipei@hackvalue.de> wrote:

Actually some users have found that its easier to grok the index by using git-gui. You can more directly see the state of update actions, and it is fairly easy to stage/unstage individual hunks of files through git-gui. Once you get that down then seeking the same methods through the command line isn't too difficult, many of the terms in git-gui are the same as the command line term, to make the transition back and forth easier for the user.

On 2007-11-23 15:58:25 -0500, Shawn O. Pearce wrote:

I spent a good chunk of time getting familiar with the index before there was a git-gui, and I can only agree: git-gui makes it obvious how simple the concept of an index really is, in a way the command-line tools never did. With the command line, you have to visualize it yourself, which means you have to understand it first; but with git-gui, it's just drawn on your screen, plain and simple.

On 23/11/07 15:58, Shawn O. Pearce wrote:

It seems that I myself did not realize what a good tool git-gui is. I started using git with the command line and so far have rarely needed to stage individual hunks (or explain the git principles to anyone). I did use gitk to visualize history (especially branches) though.

So, to sum it up, yeah, git-gui is a good way to find your way into git. After some time you realize yourself when to use the gui and when to stick to the command line.

Greetings, Jojo

Johannes Gilger wrote:

I don't know , maybe I learn differently , but
 >'Watching someone type in commands, hitting  "Pause", then trying it
 > myself'
is intuitive for me :)

I've created a screencast on using Git to manage and deploy Rails
applications.  It's not purely about Git - goes into some Rails and
Capistrano usage, but there is a good amount of practical git workflow
- pushing, pulling, branching, etc.  It's free, too.  You can
watch/download it here:

http://jointheconversation.org/railsgit

Also, if you're in the Bay Area, we're hosting a Peepcode and Pizza party on Git - where we'll show that git peepcode episode and have some git related presentations. You're welcome to come to that to learn whatever you need, if you can.

http://ruby.meetup.com/123

Lastly, if you're a rubyist, I've written pretty comprehensive ruby bindings to git that might be helpful because it's a bit more object oriented approach to using git - the examples might help.

http://jointheconversation.org/rubygit

I'm also working on a new screencast on Git that's more visual (example-wise) than most of the stuff I've seen, so I'll be happy to email that to you when it's done.

Let me know if any of that is helpful.

On Nov 26, 2007 10:33 PM, Scott Chacon <schacon@gmail.com> wrote:

nice :)

it's very useful...

On Nov 27, 2007 3:02 PM, Patrick Aljord <patcito@gmail.com> wrote:

I think you can just use 'git-init' now no need for git-init-db.

also once you've created your remote bare git rep, you don't need to use scp, you can just do: $ git-push --all git://server/remote.git

and to push there automatically: $ git remote add origin ssh://server/remote.git $ git config branch.master.remote origin $ git config branch.master.merge refs/heads/master $ git fetch $ git merge master

also for adding new files, rather than doing "git add file1 file2 file3 etc" I just do "git add ." and put in .gitignore all the files that I don't want to commit but I don't know if that's recommended :)