So I finally got my act together and published a 'pu'-like branch for StGIT. Get it at git://repo.or.cz/stgit/kha.git; gitweb at http://repo.or.cz/w/stgit/kha.git. The idea is that I grab the StGIT patches that are posted to the list, put each series in its own topic branch (based on Catalin's master), and publish a merge of them. _After_ having made sure that the test suite passes, naturally. It then becomes much easier for everyone to test these patches. This should lessen the pressure on Catalin to include patches in his master branch as soon as possible, which should in turn reduce the number of reverts in the official history. Here's what's currently in there: Karl Hasselström (8): Teach StGIT about core.excludesfile New test: make sure that popping doesn't change patch order Verify patch status during the test Make use of the get_patch() utility function Compute patch appliedness from commit DAG Test the new DAG appliedness machinery Fix bash completion after the DAG appliedness patch Speed up the appliedness test Pavel Roskin (1): Add support for SMTP over Transport Layer Security (TLS) Yann Dirson (7): Include contrib scripts in the release tarball. Improve stg-fold-files-from doc. New contrib scripts: stg-dispatch and stg-show. Add -O flag to stg-fold-files-from. Add a no-act flag to stg-dispatch and stg-fold-file-from. Provide file completion for add/resolved/refresh based on status. Fixed completion function hardcoding .git/. (Does anyone know the incantation for Junio's status mails, with topic branches grouped nicely?) NOTE: The DAG appliedness patch series is in there. They will upgrade the format of any stgit branch they touch, and there's no convenient way to change it back if you change your mind. -- Karl Hasselström, kha@xxxxxxxxxxx www.treskal.com/kalle - 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
