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

From: Michael Witten <mfwitten@gmail.com>
Date: Sep 4, 2011, 14:43 UTC
Message-ID: <CAMOZ1BtxZ5C+pH_eEBu8=oqOyY6JkP8wiFmauyqcSOeijvgA+g@mail.gmail.com>
In-Reply-To: <CACx-yZ3tav1sJnLtJOn_YugQOsM9ERi7Cc7SowunyobxxX5YdA@mail.gmail.com>

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.