Comments on: My walk through the Git book http://v1.ripper234.com/p/my-walk-through-the-git-book/ Stuff Ron Gross Finds Interesting Sun, 02 Aug 2015 11:03:35 +0000 hourly 1 https://wordpress.org/?v=4.5.3 By: ripper234 http://v1.ripper234.com/p/my-walk-through-the-git-book/comment-page-1/#comment-3725 Mon, 30 May 2011 07:23:48 +0000 http://v1.ripper234.com/?p=1470#comment-3725 Thanks @Ken for your comments, looking forward for your Git for Gits talk in two weeks.

]]> By: Ken Egozi http://v1.ripper234.com/p/my-walk-through-the-git-book/comment-page-1/#comment-3724 Mon, 30 May 2011 06:20:00 +0000 http://v1.ripper234.com/?p=1470#comment-3724 Re: How does pushing actually work?:
the if your local branch is *tracking* a remote branch, then git-push will work without arguments.
usually when you create a local branch off of a remote one (e.g. “git checkout origin/fa” & “git checkout -b fa”) it will create the new local branch (fa) as a tracking the remote one (origin/fa)

apparently from your example, pushing a local branch to a remote repo, causing a creation of a new branch on the remote, will create the same tracking relationship between the local and remote branch

]]> By: Ken Egozi http://v1.ripper234.com/p/my-walk-through-the-git-book/comment-page-1/#comment-3723 Mon, 30 May 2011 06:16:02 +0000 http://v1.ripper234.com/?p=1470#comment-3723 Re: fast forward:
see my previous comment – this simply means “moving the origin/branch” label forward until it meets “branch” label. If you think with labels in the gitk view, the whole git model becomes simple to digest

]]> By: Ken Egozi http://v1.ripper234.com/p/my-walk-through-the-git-book/comment-page-1/#comment-3722 Mon, 30 May 2011 06:14:25 +0000 http://v1.ripper234.com/?p=1470#comment-3722 Re: How can you see the ‘branch structure’ of a repository?
your conclusion is correct – git keeps track of objects, not branches.
You should treat branches (and tags) simply as labels, that mark interesting commits.

]]> By: Ken Egozi http://v1.ripper234.com/p/my-walk-through-the-git-book/comment-page-1/#comment-3721 Mon, 30 May 2011 06:11:30 +0000 http://v1.ripper234.com/?p=1470#comment-3721 Re: After I git merge without conflicts, is a git commit needed?
you do not need to commit, because git creates a commit representing the merge (does not include any change in files, but is pointing to both parent commits). gitk and see that for yourself.
So you so actually *do* need to Push it to the remote, tracked branch (assuming you have one).

]]>