So Ive started playing with git, working with several branches now. Im now (even) more convinced that this is the right strategic move for us. Once we're smoking perl-master, it seems a small step to do so for topic-branches also. Given that such branches are candidates for inclusion in core, automating their testing means that blead committers have the benefit of automated testing results to help them select patches to evaluate with their limited tuits. but Ive digressed. attached patch adds new script to generate a .gitignore file from MANIFEST. It uses a universal ignore directive (*\n), followed by negated ignore directives to *attend* to each file in MANIFEST The downside of this approach is that git-status will no longer remind you of new files youve added to the working tree, but not git-add'd. This can be fixed by narrowing the universal ignore to something like *.[oa] *.so *.exists *.bs # others are needed..Thread Next