[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] Save the Gazette!
From: |
Alaric Snell-Pym |
Subject: |
Re: [Chicken-users] Save the Gazette! |
Date: |
Wed, 16 Feb 2011 23:06:57 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; NetBSD amd64; en-US; rv:1.9.1.9) Gecko/20100520 Lightning/1.0b2pre Shredder/3.0.4 |
On 02/16/11 15:04, Andy Bennett wrote:
> 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.
>
That's a good start! Perfect! It doesn't seem to *do* anything for me
(the first sed seems to turn the output of git branch into just as many
blank lines) but, ah, we can work on such details ;-)
>
> You might get commits appearing in more than one place if the branches
> overlap.
>
That's fine, the human can easily tidy up such niggles.
ABS
--
Alaric Snell-Pym
http://www.snell-pym.org.uk/alaric/
Re: [Chicken-users] Save the Gazette!, Andy Bennett, 2011/02/16
- Re: [Chicken-users] Save the Gazette!,
Alaric Snell-Pym <=
Re: [Chicken-users] Save the Gazette!, Andy Bennett, 2011/02/17