1
Mapping between Git and Bazaar is generally straightforward.
6
All revision ids created in this mapping format are prefixed with "git-v1:".
7
This mapping format does not support roundtripped revisions from Bazaar;
8
pushing or pulling from Bazaar into Git is not possible. dpush is possible
9
and more or less does the opposite of the mapping described in this section.
14
Git commits are mapped to Bazaar revisions.
16
Bazaar revision ids are created by prefixing the (hex format) of git commit
19
Commit properties are as follows:
21
* git committer string: mapped to the Bazaar committer string
22
* git committer timestamp: mapped to the Bazaar commit timestamp
23
* git author string: mapped to the Bazaar 'author' revision property, if it
24
is different from the committer string
25
* git author timestamp: ignored
26
* git commit message: mapped to Bazaar commit message
28
The git committer string, author string and commit message are assumed to
29
be encoded in UTF-8. Any utf-8-invalid characters are ignored.
33
Git trees are generally converted to Bazaar directories, Git blobs are
34
generally converted to Bazaar files and symlinks.
36
Since all git trees are mapped *including* the root tree, it is only possible
37
to create mapped rich-root revisions.
39
File ids for all objects are simply created by taking their path and
40
escaping invalid characters in them:
43
* spaces are mapped to _s
44
* \x0c is mapped to _c