Comment 5 for bug 931994

Thx for repoening. It's always better to have a clutterd refs (which I could simply cleanup) until there is an "optimal" solution. I enjoy this really easy bzr-revid<=>git-SHA mapping "API".

However the content of any .git/ref file can really be only one single SHA1 I'd assume. :-<

Maybe you could mimik something like git notes, or even just merely use the git notes "implementation" to track the bzr revisions-id?

git notes simply keeps the last SHA1 in the refs/notes/NAMESPACE (NAMESPACE defaults to commit) and whenever they update it they track the former SHA1 via the parent object, so you can traverse the "history" via git log.

git notes --ref=bzrrevid -m 'REVIDFROMBAZAAR' would be a way to do it in "plain git"

Thx for your support and listening!