Refreshed and face-lifted README.  Tested with Chaos Calmer.  Worked wit...

This is the pull request I said I'd make earlier today.
Yeah, we were divided here as well.  My sense is that it's a fairly big
pain point to have to restart the compile just to get an error on which to
seek help (you watched me drain an hour to this today), so it makes sense
to tell them how to pipe it.

Also, people who are using this project are probably about at the point
where they can use a (re-)fresher on piping stdout and sterr.  :-)

One solution if we want to report progress is to add & tail -f output.log
error.log


On Tue, Aug 12, 2014 at 9:04 PM, Finn <notifications@github.com> wrote:

> In README.md:
>
> >
> > -    $ make -j 4
> > +    $ make -j4 V=s 1>output.log 2>error.log
>
> I would personally say not to to redirect the output as its mostly useless
> unless something goes wrong, and this way you get no idea of the progress
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/SeattleMeshnet/meshbox/pull/17/files#r16153044>.
>



-- 
Justin Holmes
Chief Chocobo Breeder, slashRoot

slashRoot: Coffee House and Tech Dojo
New Paltz, NY 12561
845.633.8330