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

From: Jakub Narebski <[email-masked]>
Date: Sun, 04 Sep 2011 08:39:24 -0700 (PDT)

Michael Witten <[email-masked]> writes:
> On Sun, Sep 4, 2011 at 14:30, knittl <[email-masked]> 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