I don't understand the details of this issue, but my instinct would be to use the T card to avoid an incompatibility.
On 3/31/17, Jan Nijtmans <jan.nijtm...@gmail.com> wrote: > 2017-03-30 21:24 GMT+02:00 Richard Hipp: >> On 3/30/17, Jan Nijtmans <jan.nijtm...@gmail.com> wrote: >>> Ping ..... Could this be decided for Fossil 2.2? Please? >> >> libfossil is a non-trivial undertaking. Because of the way Fossil is >> currently architected, libfossil is basically a ground-up rewrite. > > Hm. My question had no relation to libfossil, it was related to this > requested feature: > > <https://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg24595.html> > > Allowing Git tag comments is already implemented by Roy Marples, and I > modified it a little bit. The question is: Should a 'C' card be used for the > tag comments (which causes a format incompatibility), or should we use > the - already existing - 'T' card. > > It's just a matter of deciding which would be best, Roy and I differ in > opinion. So, Richard, if you indicate which version "roy-export" or > "jn-export" you prefer, then that's one less hurdle for GIT people > to switch to fossil ;-) Would be nice for fossil 2.2 anyway. > > Details can be found in the above link to the fossil-users mailing list. > > Thanks, > Jan Nijtmans > _______________________________________________ > fossil-dev mailing list > fossil-dev@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev > -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
