Uh oh!
There was an error while loading. Please reload this page.
doc: clarification for maxBuffer and Unicode output - #6030
Conversation
bnoordhuis
commented
Apr 4, 2016
TBH, it seems kind of pointless to me - most child processes will simply ignore it - and it's already perfectly possible to set an environment variable. I don't really see why this should be in core. |
jasnell
commented
Apr 4, 2016
Fair enough. What do you think about the docs change, however? |
bnoordhuis
commented
Apr 5, 2016
The change to the documentation LGTM if you remove the reference to |
ba28b95 to
b693babCompareb693bab to
1f02970Comparejasnell
commented
Apr 9, 2016
@bnoordhuis ... updated so that it's just the documentation changes. Also cleaned up some errant line-wrapping issues and end-of-line-whitespace. PTAL |
bnoordhuis
commented
Apr 9, 2016
LGTM |
1 similar comment
benjamingr
commented
Apr 10, 2016
LGTM |
Clarify caveats on `maxBuffer` with regards to Unicode output. Refs: nodejs#1901
1f02970 to
b968cc3Comparejasnell
commented
Apr 10, 2016
Landed in ad2df3a |
MylesBorins
commented
Apr 11, 2016
@jasnell lts? |
MylesBorins
commented
Apr 21, 2016
@jasnell lts? |
jasnell
commented
Apr 21, 2016
+1
|
MylesBorins
commented
May 17, 2016
@jasnell not landing cleanly, would you like to backport? |
jasnell
commented
May 17, 2016
will do |
MylesBorins
commented
Aug 30, 2016
ping @jasnell |
jasnell
commented
Aug 30, 2016
Thanks for the reminder, will do this week. |
MylesBorins
commented
Nov 18, 2016
@jasnell added don't land. Feel free to still open a backport PR |
Pull Request check-list
make -j8 test(UNIX) orvcbuild test nosign(Windows) pass withthis change (including linting)?
test (or a benchmark) included?
existing APIs, or introduces new ones)?
Affected core subsystem(s)
doc
Description of change
Clarify caveats on
maxBufferwith regards to Unicode output.Refs: #1901