Document pull-req #6424 in release-notes #6751
Conversation
doc/release-notes.md
Outdated
There was a problem hiding this comment.
Hmm? What specifically do you think I should change?
There was a problem hiding this comment.
-constant opcodes. (OP_1 to OP_16)
+constant opcodes (OP_1 to OP_16).
ie. move the dot at the end.
petertodd
force-pushed
the
pull-req-6424-release-notes
branch
from
2817dc9 to
c66472b
Compare
There was a problem hiding this comment.
The same here. Sorry, I haven't seen it at first somehow.
|
ACK. But I really would like to see git commit title/description understandable from a non github perspective. Keeping the mindset decentralized even at the place where the source code is managed is probably a good thing. As @laanwj once mentioned, the issue/PR number within a commit title/description is okay. But still it should be understandable from a non GitHub perspective. |
|
+1 on a readable commit message. |
|
@jonasschnelli Sure, tell me what you want it to be and I'll make it that. |
|
What about: Mention now allowed sequence of pushdatas in OP_RETURN outputs in release notes. |
Mention now allowed sequence of pushdatas in OP_RETURN outputs in release notes.
petertodd
force-pushed
the
pull-req-6424-release-notes
branch
from
c66472b to
9204930
Compare
|
@paveljanik done |
5 participants
No description provided.