Make docs for console.time and console.timeEnd more complete

[markstos]

console.time() and console.timeEnd() are very closely related. It's useful to reference them both from each other.

[sam-github]

Wrap to 80 colums, but otherwise looks much improved.

[sam-github]

Looks good to me, the existing docs were pretty lacking, but can you squash the two commits and wrap to 80 columns?

[markstos]

This PR has been updated to squash previous commits and wrap at 80 lines as requested.

[bnoordhuis]

@markstos LGTM but can you make the commit log conform to what is outlined in CONTRIBUTING.md? Be as descriptive as possible in the first line; 'more complete' is too unspecific.

Bonus points if you turn the references into links. It works like this:

Bla bla [`foo`][#link_to_foo] bla bla.

Where you pluck #link_to_foo from the HTML that make doc writes to out/doc.

[markstos]

Ben,

I've reformatted the commit message as requested and added the links as
well.

On Tue, Dec 23, 2014 at 10:03 AM, Ben Noordhuis notifications@github.com
wrote:

@markstoshttps://github.com/markstos LGTM but can you make the commit
log conform to what is outlined in CONTRIBUTING.md? Be as descriptive as
possible in the first line; 'more complete' is too unspecific.

Bonus points if you turn the references into links. It works like this:

Bla bla [foo][#link_to_foo] bla bla.

Where you pluck #link_to_foo from the HTML that make doc writes to
out/doc.

Reply to this email directly or view it on GitHub
#198 (comment).

Mark Stosberg
Senior Systems Engineer
RideAmigos

[bnoordhuis]

Landed in 6af9483, thanks Mark! I reworded the first line to fit in 50 characters.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/28933/

[jasnell]

@nodejs/build ... any explanation why we're getting CI runs on old PRs? This is at least the second one I've seen today.

[richardlau]

@jasnell It's the CI's being started for the security releases and is kind of related to https://github.com/nodejs/github-bot/issues/245 (in that the build jobs are always passing node as the repository name to the bot). There's an added kink in that the jobs and the bot assume the org is nodejs while the security CI's are nodejs-private.

[jasnell]

Oy, that's not great. Ok, thanks for the explanation :)

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/28947/