On Mon, 28 Dec 2009, Carlos Santana wrote:
Thanks for the reply David.
I think 'tagged directory' wasn't the appropriate phrase here.
In Subversion like systems branches and tags are same, i.e., both are
created using 'svn copy'. Branches are generally created for separate
line of development and tags for releasing software. So developers
follow convention of not checking in anything into tags. Otherwise
they are same.
I know that creating branches/tags doesn't involve copying files into
new directory in case of git. It will act as a pointer and make note
of changes thereafter. What I am not sure is difference between
branches and tags. Is it left to developer to follow subversion like
convention or git provides some mechanism to 'lock' tags?
git works very differently than subversion. All of git history is a
branching tree of commits, all that a tag is is a pointer to a particular
commit somewhere in this tree. it does not have the be the most recent
commit on the branch.
all branches are (pretty much) equal, you can commit and do development on
any branch.
as you say above, branches are seperate lines of development and tags can
point at releases, but when you have a branch that you are doing
development on, you don't have to stop doing development there when you do
a release, anyone who checks out the tag will get the same thing no matter
what additional development you do on that branch in the future.
does this help?
David Lang
-
CS.
On Mon, Dec 28, 2009 at 2:25 PM, <david@xxxxxxx> wrote:
On Mon, 28 Dec 2009, Carlos Santana wrote:
I would like to know if there is any difference between branches and
tags. Is it only conceptual - convention to be followed by a developer
or some technical difference? e.g. : Is it possible to create
immutable tags so that nothing can be checked in to that 'tagged
directory'?
tags are pointers into the tree. tags do not change.
in git directories are not tagged, so I'm not sure what you are working
towards here.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html