From: Carlos Santana <neubyr@gmail.com>
To: david@lang.hm
Cc: git@vger.kernel.org
Subject: Re: immutable tags?
Date: Mon, 28 Dec 2009 14:39:53 -0600 [thread overview]
Message-ID: <92c9564e0912281239h49f9138ena8bbb3a63a337a55@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0912281223440.24130@asgard.lang.hm>
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?
-
CS.
On Mon, Dec 28, 2009 at 2:25 PM, <david@lang.hm> 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
>
>
next prev parent reply other threads:[~2009-12-28 20:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 20:04 immutable tags? Carlos Santana
2009-12-28 20:25 ` david
2009-12-28 20:39 ` Carlos Santana [this message]
2009-12-28 21:15 ` david
2009-12-28 20:58 ` Matthieu Moy
2009-12-28 21:21 ` David Kågedal
2009-12-28 22:22 ` Carlos Santana
2009-12-28 22:22 ` Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92c9564e0912281239h49f9138ena8bbb3a63a337a55@mail.gmail.com \
--to=neubyr@gmail.com \
--cc=david@lang.hm \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).