git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Bennee <kernel-hacker@bennee.com>
To: git@vger.kernel.org
Subject: [QUESTION] What is a tag for?
Date: Tue, 17 Jan 2006 22:52:24 +0000	[thread overview]
Message-ID: <1137538344.9104.34.camel@malory> (raw)

Hi,

So I want to track Linus's 2.6 git tree as well as do a little small
time hacking. I'm not brave enough to sit on the very bleeding edge and
build what ever happens to be at the "HEAD" of the tree. However when a
kernel releases I'd like to build *that* kernel.

I keep thinking of tags like labels in the old convetional SCM case. Is
this correct? I can see once I've done my update (fetch/cogito what
ever) that these tags apear in my local tree:

22:42 alex@malory [linux-2.6] >cat .git/refs/tags/v2.6.16-rc1
f3bcf72eb85aba88a7bd0a6116dd0b5418590dbe

So what do I do with them now? Are they only for branch points? Is the
only way to know I'm building 2.6.16-rc1 to branch from it as described
in git-branch, even if I'm not planning on doing any development?

Is this part of the concept that branches are cheap and you should feel
free to create and throw them away at will?

I look forward to your elucidation and the ah! moment that finally gets
my head around git ;-)

Cheers,


--
Alex, homepage: http://www.bennee.com/~alex/
Zoe: "So.. Trap?" Mal: "Trap." Zoe: "We goin' in?" Mal: "Ain't nothin'
but a few hours out." Wash: "But, remember the part where it's a trap?"

             reply	other threads:[~2006-01-17 22:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 22:52 Alex Bennee [this message]
2006-01-17 23:05 ` [QUESTION] What is a tag for? Petr Baudis
2006-01-18  1:41 ` Junio C Hamano
2006-01-18  4:00   ` Linus Torvalds
2006-01-18  4:40     ` Junio C Hamano
2006-01-18  9:58       ` Petr Baudis
2006-01-18 10:07   ` Petr Baudis
2006-01-18 10:35 ` Andreas Ericsson
2006-01-18 18:19   ` Junio C Hamano
2006-01-18 18:50     ` Andreas Ericsson
2006-01-25  2:08       ` Junio C Hamano
2006-01-25  9:02         ` Andreas Ericsson

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=1137538344.9104.34.camel@malory \
    --to=kernel-hacker@bennee.com \
    --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).