Re: add command line option to quiet compiler messages

2016-07-26 Thread Tobin Harding
Patch Version 3 On Sat, Jul 23, 2016 at 12:29:41PM +0200, Andy Wingo wrote: > On Wed 20 Jul 2016 08:41, Tobin Harding writes: > > > On Thu, Jul 14, 2016 at 12:01:10PM +0200, Andy Wingo wrote: > >> On Wed 13 Jul 2016 06:08, Tobin Harding writes: ... > >> Please resend without tabs, please. Th

Re: add command line option to quiet compiler messages

2016-07-23 Thread Andy Wingo
Hi :) On Wed 20 Jul 2016 08:41, Tobin Harding writes: > On Thu, Jul 14, 2016 at 12:01:10PM +0200, Andy Wingo wrote: >> On Wed 13 Jul 2016 06:08, Tobin Harding writes: >> >> > While working on this I discovered that compile messages are output from >> > two >> > separate places (load.c and boo

Re: add command line option to quiet compiler messages

2016-07-20 Thread Tobin Harding
On Thu, Jul 14, 2016 at 12:01:10PM +0200, Andy Wingo wrote: > Incidentally this change will need a documentation update as well. I forgot the documentation in the last email. Excuse my git noob'ness but git is telling me that doc/ref is excluded by .gitignore, however the only two entries (refer

Re: add command line option to quiet compiler messages

2016-07-19 Thread Tobin Harding
On Thu, Jul 14, 2016 at 12:01:10PM +0200, Andy Wingo wrote: > On Wed 13 Jul 2016 06:08, Tobin Harding writes: > > > While working on this I discovered that compile messages are output from two > > separate places (load.c and boot-9.scm). Each file contains identical > > strings > > for the messa

Re: add command line option to quiet compiler messages

2016-07-14 Thread Andy Wingo
Hi :) Thanks for the patch! On Wed 13 Jul 2016 06:08, Tobin Harding writes: > While working on this I discovered that compile messages are output from two > separate places (load.c and boot-9.scm). Each file contains identical strings > for the messages. This goes against the rule of SPOT. Sad