Skip to content

BOLT #7: Correct indentation typo in channel_update message#649

Merged
t-bast merged 2 commits intolightning:masterfrom
ugamkamat:patch-2
Jul 23, 2019
Merged

BOLT #7: Correct indentation typo in channel_update message#649
t-bast merged 2 commits intolightning:masterfrom
ugamkamat:patch-2

Conversation

@ugamkamat
Copy link
Contributor

Related to pull #621

Corrected the indentation in the otherwise section in the timestamp check of the channel_update message. Both the actions that needed to be taken appeared at the same level which had to be indented.

Related to pull lightning#621 

Corrected the indentation in the otherwise section in the `timestamp` check of the `channel_update` message. Both the if appeared at the same level of otherwise.
Copy link
Contributor

@jtimon jtimon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@t-bast t-bast added the spelling These changes may be merged without additional sign off from the weekly meeting label Jul 18, 2019
@rustyrussell
Copy link
Collaborator

This indentation seems wrong, see https://github.com/lightningnetwork/lightning-rfc/blob/master/.copy-edit-stylesheet-checklist.md

Indentations are supposed to be 2 spaces.

@ugamkamat
Copy link
Contributor Author

@rustyrussell Thanks for pointing that out. I was oblivious of the accepted formatting for lightning docs. I have made the changes.

Copy link
Collaborator

@rustyrussell rustyrussell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ack 92df5d7

Please squash these together before commiting to master!

@t-bast t-bast merged commit 1810eaf into lightning:master Jul 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

spelling These changes may be merged without additional sign off from the weekly meeting

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants