Will re-basing support be added into Bazaar core ?

[Teemu Likonen]

On 2009-04-22 16:57 (+1000), Ben Finney wrote:

> I don't have these “ref” concepts. Is it correct for me to think of
> “ref” as “revision”, and “reflog”as “revision ancestry”?

No. I'll copy and paste from the Git glossary:

    ref
        A 40-byte hex representation of a SHA1 or a name that denotes a
        particular object. These may be stored in $GIT_DIR/refs/.

    reflog
        A reflog shows the local "history" of a ref. In other words, it
        can tell you what the 3rd last revision in _this_ repository
        was, and what was the current state in _this_ repository,
        yesterday 9:14pm. See git-reflog(1) for details.

    [...]

    symref
        Symbolic reference: instead of containing the SHA1 id itself, it
        is of the format ref: refs/some/thing and when referenced, it
        recursively dereferences to this reference. HEAD is a prime
        example of a symref. Symbolic references are manipulated with
        the git-symbolic-ref(1) command.

See "git help glossary" or:
    
    http://www.kernel.org/pub/software/scm/git-core/docs/gitglossary.html

In Git, branches are symrefs, that is, symbolic references which point
to a commit object. When user creates a new commit the branch-symref
will point to the new commit object. User can also modify that
branch-symref with "git rebase" or "git reset", for example. The manual
also talks about "git symbolic-ref" which is a low-level command I have
never heard of before. :-)

Tags are symrefs too but they can't be moved.