GIT: is a unique tag for commit?

Question

If you can use the tag only once (unique by commit), what should I do with 7 commits in the tag " Version 7.3"? I hate that GIT does not do version numbers (e.g. SVN :)).

I suppose that the subquery would be:
What would be good practice for the version number of the “Control” (Ref changes, so I want to keep major.minorin every commit and EXACTLY in each branch (I do> = 1 branch per minor)).

The first question has an actual answer (I think).
Secondly, this is the best research method.

Many thanks! I learned a lot from GIT from stackoverflow FTW!

Answer 1

I am not sure what your first question is, but I can answer the second question for you.

Just tag each version. 'v1.0', 'v1.1', 'v2.0'. Tags are completely separate from the branches, so the way you decide to process the tags does not depend on how you decide to process the branches.

For example, if your repo looks like this:

A--B--C--D--E  <- master
   \
    --C'-D'-E' <- test_branch

You can apply the tag to the branch E'and delete it safely test_branchwithout losing the code in E'. For this reason, it’s rare for people to maintain git branches for historical releases. Mark the release with the version number and feel free to delete any branches that you no longer need.

FWIW, , . , ( ) . - , .

---

re: .

: " "? , ?

, . , , , .

@VonC git -describe . , . , , , git describe - "v1.0". - "v1.0-10-abcd1234", , 10 v1.0 , .

Answer 2

, (, kubi , ).
, , ( "push" ).

Git, , " ".

git - .
. " , Git , , " .