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

Lost association between TAGS and COMMITs when rebased a git(1) repository

From
Michael Witten <mfwitten@gmail.com>
Date
Sep 4, 2011, 13:40 UTC
Message-ID
<3c10d6593152436c9dd3a5b5773e3c79-mfwitten@gmail.com>
In-Reply-To
<FF0364F3D5244CA4987EDDCFE7244BF3@urbanjsPC>
On Sat, 3 Sep 2011 21:32:03 -0400, John S. Urban wrote:
> With my first use of git(1) I  created a small project with about 200
> "commits".  When this was complete, I needed to label each commit with
> information pointing it to a section of a document.
What exactly does that mean?
> I used tags for this.

It sounds like `git notes' or rewritten commit messages would be what is appropriate.

> So far, everything was fine. I was then asked to merge two commits
> into one. I then did a "rebase" (for the first time).

You mean `squash'; the term `merge' has a specific meaning in git nomenclature.

Show 5 quoted lines
> Also, I have some commits with multiple tags pointing to them. It has come
> to my attention that might not be an intentional feature. I could find
> nothing in the documentation explicitly stating multiple tags were allowed
> to point to a commit; but the tags seem to be unique "objects" so I
> see no reason this should not be an expected feature?

Well, everybody, it sounds like John's confusion is a good example for why `tag' is another TERRIBLE choice of terminology.

See here:
  http://article.gmane.org/gmane.comp.version-control.git/179609
  Message-ID: <CAMOZ1Btmk86vmp1gRuCfG7yRuc6fD3_oYBvtq2VKK9Ywu8ay0A@mail.gmail.com>
  http://article.gmane.org/gmane.comp.version-control.git/179942
  Message-ID: <CAMOZ1Bti3ZtAEOtLiUYSkWE+rO_VQd09NAn58Cn4hZBu8f-aFQ@mail.gmail.com>
Previous: Michael WittenNext: Philip Oakley
Message 4 of 20 in “Lost association between TAGS and COMMITs when rebased a git(1) repository”
  1. John S. UrbanSep 4, 2011
  2. PJ WeisbergSep 4, 2011
  3. Michael WittenSep 4, 2011
  4. Michael WittenSep 4, 2011
  5. Philip OakleySep 4, 2011
  6. knittlSep 4, 2011
  7. knittlSep 4, 2011
  8. Michael WittenSep 4, 2011
  9. Jakub NarebskiSep 4, 2011
  10. Tor ArntsenSep 4, 2011
  11. Thomas RastSep 4, 2011
  12. Tor ArntsenSep 4, 2011
  13. John S. UrbanSep 4, 2011
  14. Documentation: "on for all" configuration of notes.rewriteRefThomas Rast, Sep 4, 2011
  15. Tor ArntsenSep 4, 2011
  16. Jeff KingSep 7, 2011
  17. Thomas RastSep 7, 2011
  18. Jeff KingSep 7, 2011
  19. Michael WittenSep 4, 2011
  20. John S. UrbanSep 4, 2011

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.