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

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

From
Michael Witten <mfwitten@gmail.com>
Date
Sep 4, 2011, 14:38 UTC
Message-ID
<CAMOZ1Btu=TOSqJu9uu3if_RFH6UQco+dFv-edVNoW9SauVQdmQ@mail.gmail.com>
In-Reply-To
<CA+sFfMcMgPDyCi6SCS=Sc4XFrug_Ee7vbmBBkmkwfwwpXg8yCg@mail.gmail.com>
On Sun, Sep 4, 2011 at 14:16, Brandon Casey <drafnel@gmail.com> wrote:
> That's true, but git is also a tool with a purpose and tags are intended to
> be permanent.

Tag *objects* are intended to be permanent (like commit objects); however, don't forget about `lightweight' tags.

> A valid workflow would need to be demonstrated before such a
> high-level operation as rebase made it so trivial to rewrite tags methinks.
How is it any different than doing the same with commits?

Let's say I have a private repository with an appreciable graph of commits and collection of tags, and that I want to clean up the history a bit before publishing it publicly. Well, it might save me a lot of trouble if I could use `rebase' to create an alternative history without also having to dicker around with creating the associated tags.

Previous: Jeff KingNext: John S. Urban
Message 19 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.