git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git "tag" objects implemented - and a re-done commit

From
AGAndreas Gal <gal@uci.edu>
Date
Apr 25, 2005, 20:23 UTC
Message-ID
<Pine.LNX.4.58.0504251318290.11481@sam.ics.uci.edu>
In-Reply-To
<Pine.LNX.4.58.0504251213530.18901@ppc970.osdl.org>

Are tag objects referenced by trees (and thus limited in scope) or are they stand-alone entities in the repository? The latter would be bad for shared object storages. Also, if I delete and recreate tags, will the old tag remain in the tree or will the file in the object storage disapear? So far all objects were always persistent, which is a nice property to have.

Andreas
On Mon, 25 Apr 2005, Linus Torvalds wrote:
Show 41 quoted lines
> 
> Ok, I just pushed out my "tag" object implementation, and due to some
> local braindamage over here, I ended up re-doing one commit, so if you
> happened to pull my 'git' tree at _just_ the right time, you will have a
> commit object named 06a02346f6a2e9ff113c189629ff7148f5141bb0 in your git 
> repository, which is not exactly bogus, but which I ended up undoing.
> 
> So if you've been pulling my git stuff, check your "git log" for whether
> you find that commit in your stuff. If you do, I guess it doesn't much
> matter (ie should all merge in cleanly), but if you want to match my tree,
> you should first undo it if it's your HEAD commit (by setting your HEAD to
> the _parent_ of that commit, and then running the git-prune-script thing).
> 
> Anyway, I decided that my original model for tags was the right one, with 
> a trivial extension. Notably, if you want to tag a single file or a tree 
> object, go wild. The tag object format is:
> 
> 	object <sha1>
> 	type <type>
> 	tag <tag>
> 	.. free-form commentary and signature of this all ..
> 
> and the "git-mktag" program verifies that the three first lines are valid 
> before it accepts it and writes it as a git object.
> 
> Right now the tags don't do anything, except fsck can verify them (not the
> signature - git doesn't even specify any particular format, and you may
> validly have unsigned tags in your tree), and will print out something
> like
> 
> 	tagged commit e83c5163316f89bfbde7d9ab23ca2e25604af290 (v2.6.12-rc2)
> 
> if you were to have such a tag-object in your object database (you don't, 
> because I've not generated one, but hey..)
> 
> 		Linus
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
Previous: Linus TorvaldsNext: Linus Torvalds
Message 2 of 14 in “git "tag" objects implemented - and a re-done commit”
  1. Linus TorvaldsApr 25, 2005
  2. Andreas GalApr 25, 2005
  3. Linus TorvaldsApr 25, 2005
  4. Andreas GalApr 25, 2005
  5. Linus TorvaldsApr 25, 2005
  6. Linus TorvaldsApr 25, 2005
  7. SeanApr 26, 2005
  8. Ryan AndersonApr 26, 2005
  9. Matthias UrlichsApr 27, 2005
  10. Linus TorvaldsApr 27, 2005
  11. H. Peter AnvinApr 25, 2005
  12. Linus TorvaldsApr 25, 2005
  13. Petr BaudisApr 25, 2005
  14. Linus TorvaldsApr 25, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.