Hi Jon! I guess what people are pointing at is that you can: - run your import - publish that as mozilla-historical.git - copy that to mozilla.git - rm all the old heads from mozilla.git - rm all the 'new' heads from mozilla-historical.git - run git-repack -a -d on both - make the historical repo read-only later, it is trivial to 'archive' branch. Similarly, other projects run a repo-per-developer or perhaps thematic repos. No point in painting 'policy' when usage practices suffice. By the way, gitk doesn't show all the branches by default. You have to pass --all, which stands for... all ;-) maybe gitk should have --recent-heads. However, I use --since=3.months.ago all the time, and it works great. cheers, martin - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html