Git, defining branch boundaries

F

falstaf2011-09-06 08:52:16

git

falstaf, 2011-09-06 08:52:16

How, after merging a branch with another, to determine its boundaries in the general chain of commits?

Thanks in advance for any help.

Reply

Answer the question

In order to leave comments, you need to log in

3 answer(s)

D

Dmitry404, 2011-09-06
@Dmitry404

As far as I know, in the case of fast-forward merge, in order to avoid this, do the merge with the --no-ff parameter, which will create a commit object when merging.

L

lesha_penguin, 2011-09-06
@lesha_penguin

Your best bet is to look at git log --graph , which will at least give you a visual idea of what branched and merged and when.
The concept of "boundary" for such non-linear version control systems as git is very arbitrary. You can have a whole tree of development branches branching off from the main or from other development branches, and then merging many times.

U

umcherrel, 2011-09-06
@umcherrel

Question: what will knowledge give you where the branch began?
Consider the situation: example
We made a topicA branch from commit E, after several commits in topicA (A, B), the development of this branch went in two directions topicA and topicB
So where does topicB grow its legs from? Someone will think that this is commit B. After a while, it turned out that the development of topicA was a dead end and the branch was deleted. So where did topicB come from?