Skip to content

Conversation

pinheadmz
Copy link
Member

@sipa
Copy link
Member

sipa commented Feb 16, 2016

utACK

@paveljanik
Copy link
Contributor

ACK pinheadmz@7f01e4e
Right, using "index" instead of "position" is better here.

@@ -1444,7 +1444,7 @@ UniValue listtransactions(const UniValue& params, bool fHelp)
" \"trusted\": xxx (bool) Whether we consider the outputs of this unconfirmed transaction safe to spend.\n"
" \"blockhash\": \"hashvalue\", (string) The block hash containing the transaction. Available for 'send' and 'receive'\n"
" category of transactions.\n"
" \"blockindex\": n, (numeric) The block index containing the transaction. Available for 'send' and 'receive'\n"
" \"blockindex\": n, (numeric) The position of the transaction in the block that includes it. Available for 'send' and 'receive'\n"
Copy link
Contributor

Choose a reason for hiding this comment

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

tiny nit: position seems slightly non-conventional?

The index of the transaction in the block that includes it.

Copy link
Member

Choose a reason for hiding this comment

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

Agreed with this slight re-phrasing

Copy link
Member

Choose a reason for hiding this comment

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

I'd prefer to stick with index too. It has a well-defined meaning, while position is too general (it could be a byte offset, or a set of 3D coordinates within the unit block...).

Copy link
Member Author

Choose a reason for hiding this comment

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

cool, updated

@dcousens
Copy link
Contributor

utACK 7f01e4e

@laanwj laanwj added the Docs label Feb 17, 2016
@instagibbs
Copy link
Member

utACK

@paveljanik
Copy link
Contributor

ACK pinheadmz@ef40f6b after squash

@jonasschnelli
Copy link
Contributor

ACK ef40f6b0703fb2004183b85bdd2fb9e88b58b349.

@laanwj
Copy link
Member

laanwj commented Feb 18, 2016

Before merging, can you please squash these changes into one commit? e.g.

$ git rebase -i 8b70a64

In the editor, replace the second 'pick' with 'f', then save and exit.
Then, force-push the result to this branch with

git push -f origin master

@pinheadmz
Copy link
Member Author

@laanwj thanks for your help

@laanwj laanwj merged commit 7eef1d0 into bitcoin:master Feb 19, 2016
laanwj added a commit that referenced this pull request Feb 19, 2016
7eef1d0 Clarify description of blockindex (Matthew Zipkin)
@maflcko
Copy link
Member

maflcko commented Feb 26, 2016

@laanwj I guess this could be backported to 0.12.1

Also, Post-merge ACK.

maflcko pushed a commit to maflcko/bitcoin-core that referenced this pull request Apr 27, 2016
@maflcko
Copy link
Member

maflcko commented Jun 9, 2016

Backported as part of #7938. Removing label 'Needs backport'.

thokon00 pushed a commit to faircoin/faircoin that referenced this pull request Jun 28, 2016
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants