All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Kågedal" <davidk@lysator.liu.se>
To: git@vger.kernel.org
Subject: Re: immutable tags?
Date: Mon, 28 Dec 2009 22:21:25 +0100	[thread overview]
Message-ID: <87d41yvlpm.fsf@krank.kagedal.org> (raw)
In-Reply-To: 92c9564e0912281204h13c6a566w95069023e6909eda@mail.gmail.com

Carlos Santana <neubyr@gmail.com> writes:

> 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'?

You are always in full control of your own repository, and have no
control over what other people do with their's. So you can't prevent
other people from changing the tags in their private repos, but you can
prevent them from propagating these changes back to you, or to a central
repository you control.

But perhaps there is nothing to worry about. I think the git commands
won't modify a tag unless you force it.

Also, if you use signed tags, you can be sure that they are not silently
replaced while still claiming to be tagged by you.

-- 
David Kågedal

  parent reply	other threads:[~2009-12-28 21:22 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
2009-12-28 21:15     ` david
2009-12-28 20:58 ` Matthieu Moy
2009-12-28 21:21 ` David Kågedal [this message]
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=87d41yvlpm.fsf@krank.kagedal.org \
    --to=davidk@lysator.liu.se \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.