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
Jakub Narebski <jnareb@gmail.com>
Date
Sep 4, 2011, 15:39 UTC
Message-ID
<m362l848sw.fsf@localhost.localdomain>
In-Reply-To
<CAMOZ1BtxZ5C+pH_eEBu8=oqOyY6JkP8wiFmauyqcSOeijvgA+g@mail.gmail.com>
Michael Witten <mfwitten@gmail.com> writes:
Show 16 quoted lines
> On Sun, Sep 4, 2011 at 14:30, knittl <knittl89@googlemail.com> wrote:
> 
> > "Rebase" takes commits and creates new commits from those. The new
> > commits are not the same as the old, although they might have
> > associated the same tree or changeset.
> 
> According to `git help glossary':
> 
>   changeset
>       BitKeeper/cvsps speak for "commit".
>       Since git does not store changes, but states,
>       it really does not make sense to use the term
>       "changesets" with git.
> 
> Git's erroneous nomenclature is bad enough as it is, so please try
> not to explain things using such spurious terminology.

Actually "changeset", at least in the original meaning as the set of changes (the difference between two snapshots), is perfectly in place here: rebase operation preserves changes which means that it copies changesets, at least if there are no conflicts.

-- 
Jakub Narębski
Previous: Michael WittenNext: Tor Arntsen
Message 9 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.