> it might help if you describe what you mean by "getting stuck"
Stuck is a poor choice. Let me elaborate. I have a git repository that has 302 commits in it. Most of them existed before I installed bloodhound (a couple weeks ago). After adding the repo and running the initial sync via trac-admin, bloodhound shows the first 27 commits in the repo, the last of which was about 7 months ago. That last commit happens to also be one of my few tagged commits. It's tagged with a version number "1.3.4". My hunch is that trac is stopping at this tag and not looking for any more. Maybe there's some config in trac git where I need to specify the branch to follow? It sounds like this is a trac issue, but my first experience with trac is through bloodhound here. Is there a specific logfile I should be looking at? Thanks for the responses -Dan
