Re: What's cooking in git.git (Jun 2017, #09; Fri, 30)
- From
Stefan Beller <sbeller@google.com>
- Date
- Jul 5, 2017, 00:17 UTC
- Message-ID
- <CAGZ79karazektmWg0nneYnfGU29dm8BtPUndOCobetH4xSy=tg@mail.gmail.com>
- In-Reply-To
- <xmqq8tk4loyr.fsf@gitster.mtv.corp.google.com>
On Mon, Jul 3, 2017 at 11:02 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 32 quoted lines
> "Philip Oakley" <philipoakley@iee.org> writes: > >> From: "Junio C Hamano" <gitster@pobox.com> >> >>> I am not sure what you are asking. Is this the command you are >>> looking for? >>> >>> $ grep -e "^[[*]" whats-cooking.txt >>> >> Ah, thanks. >> >> It does presume that one has extracted the email to the text file, >> which is easier on some systems and mail clients than others ;-) > > Perhaps you would want to find an e-mail client that can handle text > files better, then? ;-) > > If you are cloning and following along my tree from one of these > places: > > git://repo.or.cz/alt-git.git/ > git://git.kernel.org/pub/scm/git/git.git/ > git://github.com/git/git.git/ > > the 'todo' branch in these repositories keeps track of the > whats-cooking.txt report (among other things), so you can also: > > $ git cat-file -p origin/todo:whats-cooking.txt | > grep -e "^[[*]" > > to get the same effect. >
FWIW: I have a script in my git dir,
cat git/cookreport.sh git -C Meta pull origin todo Meta/cook -w
with Meta being a repo tracking one of the URLs above.
I might add a | grep -e "^[[*]" or add some scripting to verbose report my own topics.
Thanks, Stefan