From: Eric Sunshine sunsh...@sunshineco.com
On Sun, Jul 19, 2015 at 4:08 PM, Philip Oakley philipoak...@iee.org
wrote:
Keep the build clean of extraneous files if it is indeed clean.
Otherwise leave the msvc-build-makedryerrors.txt file both as
a flag for any CI system or for manual debugging.
On Mon, Jul 20, 2015 at 2:16 AM, Philip Oakley philipoak...@iee.org wrote:
From: Eric Sunshine sunsh...@sunshineco.com
On Sun, Jul 19, 2015 at 4:08 PM, Philip Oakley philipoak...@iee.org
wrote:
Keep the build clean of extraneous files if it is indeed clean.
Otherwise leave the
From: Eric Sunshine sunsh...@sunshineco.com
On Mon, Jul 20, 2015 at 2:16 AM, Philip Oakley philipoak...@iee.org
wrote:
From: Eric Sunshine sunsh...@sunshineco.com
On Sun, Jul 19, 2015 at 4:08 PM, Philip Oakley
philipoak...@iee.org
wrote:
Keep the build clean of extraneous files if it is
On Mon, Jul 20, 2015 at 7:55 AM, Philip Oakley philipoak...@iee.org wrote:
From: Eric Sunshine sunsh...@sunshineco.com
Although that works, I'm not sure that it's really all that desirable
due to the unnecessary and potentially confusing 'for' loop. I'd
probably just write it as:
unlink
On Sun, Jul 19, 2015 at 4:08 PM, Philip Oakley philipoak...@iee.org wrote:
Keep the build clean of extraneous files if it is indeed clean.
Otherwise leave the msvc-build-makedryerrors.txt file both as
a flag for any CI system or for manual debugging.
Note that the file will contain the new
5 matches
Mail list logo