Make sure LogPrint strings are line-terminated #6599

Merged
merged 1 commit into from Aug 31, 2015

Conversation

Projects
None yet
5 participants
@rnicoll
Contributor

rnicoll commented Aug 29, 2015

Seems to have been missed in #6497, but do let me know if there's a reason this shouldn't have a new line at the end.

@jonasschnelli

This comment has been minimized.

Show comment
Hide comment
@jonasschnelli

jonasschnelli Aug 29, 2015

Member

utACK.

Member

jonasschnelli commented Aug 29, 2015

utACK.

@fanquake

This comment has been minimized.

Show comment
Hide comment
@fanquake

fanquake Aug 30, 2015

Member

utACK

Member

fanquake commented Aug 30, 2015

utACK

@paveljanik

This comment has been minimized.

Show comment
Hide comment
@paveljanik

paveljanik Aug 30, 2015

Contributor

ACK

Contributor

paveljanik commented Aug 30, 2015

ACK

@laanwj

This comment has been minimized.

Show comment
Hide comment
@laanwj

laanwj Aug 31, 2015

Member

utACK
Seems that I missed this, due to some other debug prints in net that do lack \n for a reason (as they're part of a set of multiple prints).

Member

laanwj commented Aug 31, 2015

utACK
Seems that I missed this, due to some other debug prints in net that do lack \n for a reason (as they're part of a set of multiple prints).

@laanwj laanwj merged commit 9bebf60 into bitcoin:master Aug 31, 2015

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

laanwj added a commit that referenced this pull request Aug 31, 2015

Merge pull request #6599
9bebf60 Make sure LogPrint strings are line-terminated (J Ross Nicoll)

@rnicoll rnicoll deleted the rnicoll:missing-newlines branch Mar 13, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment