fanquake added the label
Refactoring
on May 31, 2017
jonasschnelli
commented at 8:37 am on May 31, 2017:
contributor
Concept ACK
dcousens approved
dcousens
commented at 8:53 am on May 31, 2017:
contributor
utACK
laanwj
commented at 8:27 am on June 1, 2017:
member
Concept ACK. I think we can all agree that this needs to be done at some point, though we’ll have to discuss when to do this with the least impact. This change probably means every single PR needs to be rebased.
practicalswift force-pushed
on Jun 4, 2017
practicalswift
commented at 4:53 pm on June 4, 2017:
contributor
Can you rewrite this as a series of scripted diffs (possibly mixed with a few manual commits to fix things up)? See #10189#10193#10502#10321 for examples.
As for timing, possibly immediately after the feature freeze?
practicalswift force-pushed
on Jun 8, 2017
practicalswift force-pushed
on Jun 8, 2017
practicalswift force-pushed
on Jun 8, 2017
practicalswift force-pushed
on Jun 8, 2017
practicalswift force-pushed
on Jun 8, 2017
practicalswift force-pushed
on Jun 8, 2017
practicalswift force-pushed
on Jun 8, 2017
practicalswift force-pushed
on Jun 8, 2017
practicalswift force-pushed
on Jun 8, 2017
practicalswift force-pushed
on Jun 8, 2017
practicalswift
commented at 2:29 pm on June 8, 2017:
contributor
@sipa Great idea! Now re-implemented as a scripted-diff. Looks good? :-)
practicalswift renamed this:
Use the C++11 keyword nullptr to denote the pointer literal instead of the macro NULL
scripted-diff: Use the C++11 keyword nullptr to denote the pointer literal instead of the macro NULL
on Jun 8, 2017
@practicalswift You can use sed -i 's/\<NULL\>/nullptr/g' for the main operation. \< and \> denote begin and end of word.
practicalswift force-pushed
on Jun 9, 2017
practicalswift
commented at 3:26 pm on June 9, 2017:
contributor
@sipa Good point! Now using s/\<NULL\>/nullptr/g. Looks good? :-)
practicalswift force-pushed
on Jun 11, 2017
practicalswift force-pushed
on Jun 11, 2017
practicalswift
commented at 1:53 pm on June 11, 2017:
contributor
Merge conflicts resolved!
practicalswift
commented at 9:23 am on June 13, 2017:
contributor
What is the correct protocol to follow w.r.t. rebasing a large scripted-diff PR such as this one?
Should I rebase periodically myself to keep it mergeable, or should I wait until I’m asked to rebase prior to the suggested time for merge (@sipa suggested: “possibly immediately after the feature freeze”).
MarcoFalke
commented at 10:20 am on June 13, 2017:
member
@practicalswift It is sufficient to rebase only once. Please refer to #9961#issue-212976673 for the preliminary date of feature freeze.
practicalswift
commented at 10:36 am on June 13, 2017:
contributor
practicalswift
commented at 2:17 am on June 22, 2017:
contributor
@jtimon Unfortunately that command is a bit too broad which leads to the following problems:
It would match dependencies such as src/leveldb/, src/secp256k1/, src/univalue/, etc.
It would match unrelated constants such as TX_NULL_DATA, SCRIPT_VERIFY_NULLDUMMY, SCRIPT_VERIFY_NULLFAIL, bitcoinconsensus_SCRIPT_FLAGS_VERIFY_NULLDUMMY, SCRIPT_ERR_SIG_NULLDUMMY, SCRIPT_ERR_SIG_NULLFAIL, etc.
practicalswift force-pushed
on Jun 22, 2017
jtimon
commented at 9:04 pm on June 23, 2017:
contributor
Anyway, no big deal, probably not worth it to change it. I looked at the changes and they do what I expect.
practicalswift
commented at 7:30 am on June 26, 2017:
contributor
@jtimon Unfortunately that one is too broad – it will replace NULLDUMMY with nullptrDUMMY, etc. 's/\<NULL\>/nullptr/g' is the narrowest replacement I can think of :-)
jtimon
commented at 1:59 am on June 27, 2017:
contributor
No worries, what you have seems to work. Needs rebase.
practicalswift force-pushed
on Jun 27, 2017
practicalswift
commented at 5:17 am on June 27, 2017:
contributor
Rebased! :-)
practicalswift force-pushed
on Jun 28, 2017
practicalswift force-pushed
on Jul 2, 2017
practicalswift force-pushed
on Jul 15, 2017
practicalswift
commented at 1:00 pm on July 15, 2017:
contributor
Rebased!
TheBlueMatt
commented at 7:44 pm on July 16, 2017:
member
utACK2f2ac6fc76c966b6174d9df647648d0573d2ac41. I read through the diff but not thoroughly, the script looks good :).
practicalswift force-pushed
on Jul 17, 2017
practicalswift
commented at 8:00 am on July 17, 2017:
contributor
Rebased! :-)
jtimon
commented at 1:23 am on July 18, 2017:
contributor
Fast scroll-down re-review ACK.
Didn’t checked the rebase.
practicalswift force-pushed
on Jul 24, 2017
laanwj added this to the milestone 0.15.0
on Jul 28, 2017
practicalswift force-pushed
on Aug 1, 2017
practicalswift
commented at 5:05 pm on August 1, 2017:
contributor
Rebased! :-)
promag
commented at 3:17 pm on August 6, 2017:
member
utACK2f2ac6f.
Nit, while rebasing, reword to something short, like scripted-diff: Replace NULL macro with C++11 nullptr keyword.
sipa
commented at 10:08 pm on August 6, 2017:
member
Let’s try to merge this right before branching off 0.15.
scripted-diff: Use the C++11 keyword nullptr to denote the pointer literal instead of the macro NULL
-BEGIN VERIFY SCRIPT-
sed -i 's/\<NULL\>/nullptr/g' src/*.cpp src/*.h src/*/*.cpp src/*/*.h src/qt/*/*.cpp src/qt/*/*.h src/wallet/*/*.cpp src/wallet/*/*.h src/support/allocators/*.h
sed -i 's/Prefer nullptr, otherwise SAFECOOKIE./Prefer NULL, otherwise SAFECOOKIE./g' src/torcontrol.cpp
sed -i 's/tor: Using nullptr authentication/tor: Using NULL authentication/g' src/torcontrol.cpp
sed -i 's/METHODS=nullptr/METHODS=NULL/g' src/test/torcontrol_tests.cpp src/torcontrol.cpp
sed -i 's/nullptr certificates/NULL certificates/g' src/qt/paymentserver.cpp
sed -i 's/"nullptr"/"NULL"/g' src/torcontrol.cpp src/test/torcontrol_tests.cpp
-END VERIFY SCRIPT-
90d4d89230
practicalswift force-pushed
on Aug 7, 2017
practicalswift
commented at 5:38 am on August 7, 2017:
contributor
Rebased!
@sipa That’s great! When is that expected to happen? I’ll keep this PR rebased :-)
practicalswift
commented at 5:42 am on August 7, 2017:
contributor
What about merging the related PR #10645 (“Use nullptr (C++11) instead of zero (0) as the null pointer constant “) at the same time? :-)
MarcoFalke
commented at 1:03 pm on August 8, 2017:
member
90d4d89 conflicts with #10882, which is tagged for 0.15.
practicalswift
commented at 1:42 pm on August 8, 2017:
contributor
@MarcoFalke Thanks for the notification! Should I wait until #10882 is merged and then rebase on master or what is the preferred way to handle it?
laanwj merged this
on Aug 14, 2017
laanwj closed this
on Aug 14, 2017
laanwj referenced this in commit
ce74799a3c
on Aug 14, 2017
practicalswift
commented at 2:35 pm on August 14, 2017:
contributor
This is a metadata mirror of the GitHub repository
bitcoin/bitcoin.
This site is not affiliated with GitHub.
Content is generated from a GitHub metadata backup.
generated: 2024-11-17 12:12 UTC
This site is hosted by @0xB10C More mirrored repositories can be found on mirror.b10c.me