vcs-fast-import-devs team mailing list archive

["Shawn O. Pearce" <spearce@xxxxxxxxxxx>]

Max Bowsher <maxb@xxxxxxx> wrote:
> I am working on a conversion, in which I want to refer to
> destination-VCS's commit ids in revision log messages - i.e. I want to
> insert text into commit messages which says something like
>  "Cherrypick <git-hash-or-bzr-revid-or-...-goes-here>".
> 
> The obvious problem is that the tool writing the fastimport stream
> doesn't know these, because they only get allocated by the importer.
> 
> I would like to propose that a new importer feature be declared,
> "commit-message-mark-expansion", in which the importer is expected to
> substitute substrings of commit messages looking like <{[:12345]}> with
> the destination VCS's native revision id for the given mark.

Makes sense.  But what if the message contains a literal :n?  E.g.
the message:

  Fixed URLs with non-standard ports like http://foo:8080/

If we are going to start parsing the message content we probably
should have some sort of escape that allows the frontend to protect
some of it from the replacement parsing, so literal :n can be passed
through at the same time that a different :n is updated with the
revision identifier.

-- 
Shawn.