On Fri, Jul 24, 2015 at 5:38 AM, <org.fossil-scm.fossil-us...@io7m.com>
wrote:

> An initial run of "fossil export | git fast-import" seems to
> show no pgp signatures in the resulting git repository. This doesn't
> seem unreasonable, given that it's obviously not going to be possible
> to forge new signatures!
>

I would have thought this would have worked. But I don't know enough about
how Fossil uses PGP to make signatures, nor how git-fast-export format
might support signatures to speak to this.


> Secondly: all of the committer names are... sort of bad. Most are of
> the form "<m0> m0" (m0 being the username I used there).
>

As I recall, git-fast-export files can be edited, so you could write a
script to replace the user names with your name and email address.

Note that this would invalidate the signatures that do appear in the export
file (if any are in it).

2. PGP sign all commits with the key with which they were originally
>    signed (obviously, some of these keys have expired).
>
> Obviously, I'd like to preserve the original dates and times too.
>
> I could sort of imagine replaying and re-signing the original commits
> one-by-one to achieve the above, but I'm not sure how to go about this
> or if it's even feasible.
>

Assuming that Fossil's PGP signatures aren't compatible (or otherwise can
be stored) with git, you would have to use a script to re-sign the commits
in git.

I think you can use the "fossil timeline" command to get a list of all
commits in your Fossil repo. I don't know how to get a list from a git repo.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to