document the term "ghost"

Bug #405452 reported by Samuel Bronson on 2009-07-27
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

There is a term "ghost" floating around, which I gather has something to do with revisions that aren't available locally, but am not at all sure *what*. It should be documented in some sort of "bzr help glossary" or "bzr help ghost", I think ...

Samuel Bronson (naesten) on 2009-07-27
tags: added: glossary
Martin Pool (mbp) on 2009-07-28
Changed in bzr:
status: New → Confirmed
importance: Undecided → Medium
John C Barstow (jbowtie) wrote :

maxb: "A ghost is when you know a revision was merged, but you don't know anything else about the merged revision besides its id"

Possible causes: Repository format changes, uncommits, bugs, plugin code.

Generally not be an issue for end users, however might come up during repository forensics or debugging.

Vincent Ladeuil (vila) wrote :

It could also be described as a revision that is mentioned *only* as a parent of another revision.
Only the rev_id is known, nothing else.
uncommits shouldn't create ghosts AFAIK that would be a serious bug. repo format changes either.

I also think it can be seen by users when they are generated on purpose (like some bzr-svn workflows) and should be handled as gracefully as we can.

Also, some ghosts *can* be filled if the repository that contain them is available.

If repoA doesn not contain <ghost> but repoB contains it, you can fill <ghost> by doing (untested but explaining the concept):

cd <somewhere below repoA>
bzr init dummy ; cd dummy
bzr pull -r<ghost> <some branch in repoB>
cd .. ; rm -fr dummy

Jelmer Vernooij (jelmer) on 2017-11-09
tags: added: check-for-breezy
Jelmer Vernooij (jelmer) on 2017-11-09
tags: removed: check-for-breezy
Changed in brz:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers