On 13/02/17 01:23, Roy Marples wrote:
> On 13/02/17 01:01, Roy Marples wrote:
>> 1) add an option to (or to not) export tags. The git default is not to,
>> I'm tempted to make this the fossil default as well. See *.
> 
> This is wrong. Git has no such option.
> 
>> 2) maintain a file of tags so we only export tags generated at the
>> fossil side, and even then only once. See *.
>>
>> 3) adjust fossil to store a comment for the tag. Guidance on how to do
>> this is welcome :)
>>
>> * Apparently git can sign tags with GPG. I've not tried it. This alters
>> the signature of the tag. I have no idea how fossil reacts here, but
>> will probably be OK as it can handle many tags whereas git just has the one.
> 
> I'm currently leaning towards 3, even though it's the more complicated
> because it doesn't lose data.

3 has now been implemented in the roy-export branch.
Turned out to be quite easy. A database rebuild is required though as an
extra field has been added to the tagxref table.

This means that my git <-> fossil bridge is now fully working - for my
normal work flow at least.

Summary of changes from trunk:
  *  tag committer is exported
  *  import user matching works via contact info
  *  exported branch and tag names are no longer mangled
  *  no more silent renaming of master vs trunk [1]
  *  tag importing actually works for git
  *  tag comments are imported and exported [2]

Testing now welcome.

Roy

[1] There is still the issue of the silent trunk in fossil. I don't know
if what I've done here is correct. Artifacts look like a bug, but
explicit renaming of master -> trunk works around it.

[2] You can also see the comments in the timeline, which is nice. But
there currently isn't a UI in fossil itself to enter a tag comment.
_______________________________________________
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