On Tue, Feb 15, 2011 at 2:31 PM, Mark Janssen <[email protected]> wrote: > On Tue, Feb 15, 2011 at 1:41 PM, Richard Hipp <[email protected]> wrote: >> >> >> On Sun, Feb 13, 2011 at 4:15 PM, Richard Hipp <[email protected]> wrote: >>> >>> >>> On Sun, Feb 13, 2011 at 4:09 PM, Martin Gagnon <[email protected]> wrote: >>>> >>>> I've convert a git repository to fossil and I'm a bit confuse with my >>>> tags I had in git, the way they become in fossil. >>>> >>>> I had some tag in the original git repo, which was not branch, only a >>>> tag to a particular version. Once I convert to fossil, those tag >>>> propagate to future versions until next tag is reach. Those tags >>>> seems to be like real branches after conversion to fossil. >>>> >>>> Did someone else get the same problem? Or I miss something? >>> >>> I've seen the same thing. >>> >>> Either I'm misunderstanding the git-fast-export file format documentation >>> or else git-fast-export is getting branches and tags confused. >> >> git-fast-import works and generates the correct repository for the output of >> git-fast-export. So there must be some way of interpreting the output of >> git-fast-export correctly. Anybody with clues on how to do this, please >> help! >> >> >>> >>> I'm not sure which it is, but I am leaning toward the problem being in >>> git-fast-export. Others have reported issues with that tool, and the >>> documentation for git-fast-export itself explains that it cannot >>> successfully export the Linux kernel repository.... >>> >>> I've got some ideas on how I might work around the (presumed) brokenness >>> in git-fast-export. If you are able to send me the output of >>> git-fast-export from your repository, or let me clone you git repository, >>> that will give me another example repository to work with. >>> >>> >>>> >>>> Thanks >>>> >>>> -- >>>> Martin >>>> _______________________________________________ >>>> fossil-users mailing list >>>> [email protected] >>>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >>> >>> >>> >>> -- >>> D. Richard Hipp >>> [email protected] >> >> >> >> -- >> D. Richard Hipp >> [email protected] >> >> _______________________________________________ >> fossil-users mailing list >> [email protected] >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> >> > > Maybe I am missing something here, but aren't tags simply identifiable > by commits with revision prefix /refs/tags? > > > Mark >
After some further investigation, it seems that git fast-export is making a mess of the tags. Commit commands refer to tags that have not been created yet. This does not play very well with the fossil approach of not rewriting history. I suspect the only way to solve this is to make a separate non propagating tagging phase after the whole repo has been converted. Mark _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
