Hi, > 3) A script that, when run in a local git checkout, or maybe by talking > direct to the core git repo, lists all the commits in a specified time > period, grouped by branch.
> For bonus points, the output of scripts (2) and (3) could be actual > markup for putting straight into the gazette, say as a bulleted list, > just requiring editing to remove useless commits and to add editorial > insight. This bash command, executed inside a git repo, should do the trick: ----- for b in `git branch -a --no-color | sed -e 's/^*//' -e 's/^\s*\(\S*\).*/\1/'` ; do echo " * On `echo $b | sed -e 's#^remotes/##'`:"; git log --pretty=format:' * (%h): %s (%an, %ar)' --since="1 week ago" $b; echo ""; done; ----- It's a one-liner. You might get commits appearing in more than one place if the branches overlap. Regards, @ndy -- [email protected] http://www.ashurst.eu.org/ 0x7EBA75FF
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
