Re: git pull request

thanks.
have now posted full make output at https://github.com/fontforge/fontforge/issues/1016

-v


On 2 Dec 2013, at 09:06, Daniel Kahn Gillmor <[email protected]> wrote:

> On 12/02/2013 11:54 AM, vernon adams wrote:
>> On 2 Dec 2013, at 08:38, Daniel Kahn Gillmor <[email protected]> wrote:
>>> That bug report doesn't have enough information to tell what went wrong
>>> with the build -- can you provide more logs from the "make" step?
>> 
>> Yes i can, but someone may need to tell me exactly how to do that. If i can know the best ways to run make to get detailed error reports, then i can definitely provide as much info as is needed.
> 
> Run "make", and then supply the *entire* output to the bug report, not
> just the final 15 lines.
> 
> The usual suggestions about supplying legible terminal transcripts [0]
> apply. :)
> 
> Regards,
> 
> 	--dkg
> 
> [0] https://support.mayfirst.org/wiki/terminal_transcripts
> 
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT 
> organizations don't have a clear picture of how application performance 
> affects their revenue. With AppDynamics, you get 100% visibility into your 
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk_______________________________________________
> Fontforge-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fontforge-devel


------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk