Re: several quick questions

Andreas Ericsson wrote:

git will recognize the merge-base as being the current HEAD and simply
sets HEAD to point to that of topic-branch. This is why it's called a
fast-forward, since no heavy computing needs to be done to combine the
two development tracks.

well finaly, if nothing happened in one of the lines, then the two lines
become the same, when merging back into one line. and the two lines
overlay each other. That is what i saw during playing with git-merge,
git-pull and git-reset.. ok.

quoted

do you have to make a new private branch out of the tag 1.1.6?

No, you don't, but you can if you wish. It's nifty if you want to fork
the development from a particular branch. In your case, if you really,
really *want* the arrows pointing to one line, you can do

$ git branch topic-branch HEAD^
# work, work, work
$ git checkout master
$ git pull . topic-branch

That would create one pretty arrow. When multiple tracks of development
(rather than just two) are combined into one it's called an octopus
merge. Unless you really know what you're doing, you should try to avoid
those for small projects, and doing it just for the pretty arrows is....
well, let's call it "interesting from the behaviour science scholars
point of view".

its just the thought "cool, it looks like there at the git repo"... just
to realize "ok, that happens, when i merge two trees.

quoted

i used svn and there i could go back some revisions. I haven't found
such a feature in git, yet... but i think i am blind all the time.

Most likely. I believe at least the reset command is mentioned in the
tutorial. I trust you've read it before asking, so something is amiss
either with your eyesight or the tutorial.

well the namespace of the references confused me, before i realized,
that HEAD finally points to an sha1sum (which symbolizes a certain commit)

mh.. I use pull if i want to get an external development tree, right? I
still search for a possibility to replace the svn:externals, which were
quite handy some times.

lets imagine, i want to reuse work i did in another repository, then I
can easily pull from that repository, which my work i want to reuse is
stored at... i see... i just will have to pull frequently.... and hope
there is no conflict between some files.


once more... thank you all and good work.

Nicolas