Closed Aprogiena closed 6 years ago
LOCK
External\NBitcoin\Protocol\AddressManager.cs
External\NBitcoin\Protocol\AddressManager\Behaviors\AddressManagerBehavior.cs
External\NBitcoin\Protocol\AddressManager\Behaviors\NodesGroupBehavior.cs
LOCK
Network.cs
Networks.cs
NetworkBuilder.cs
@dangershony full path pls :) to avoid confusions
@Aprogiena Im just going through my PR, I need to lock
External\NBitcoin\Protocol\Node.cs
too.
@fassadlr you can't lock Node.cs because it is locked :D and my PR is already in the queue, so you will just have conflicts. i'll unlock it as soon as PR is merged
All good @Aprogiena I just saw it now :) Its ok I can merge your changes in after.
unlocking my locks:
UNLOCK External\NBitcoin\Protocol\Node*.cs
except for NodesGroup.cs
UNLOCK
Network.cs
Networks.cs
NetworkBuilder.cs
LOCK \NBitcoin\ChainedBlock.cs
LOCK
UNLOCK
@mikedennis i guess you could unlock right?
UNLOCK \NBitcoin\ChainedBlock.cs
Will be doing more work on this later but for now it's open.
UNLOCK
External\NBitcoin\Protocol\AddressManager.cs
External\NBitcoin\Protocol\AddressManager\Behaviors\AddressManagerBehavior.cs
External\NBitcoin\Protocol\AddressManager\Behaviors\NodesGroupBehavior.cs
@fassadlr Node.cs also free now?
Ah yes @aprogiena Node.cs is unlocked.
Thank you, in which case I
LOCK
src/NBitcoin/Protocol/*
src/NBitcoin/Utils.cs
src/NBitcoin/UInt256.cs
UNLOCK
src/NBitcoin/Protocol/*
src/NBitcoin/Utils.cs
src/NBitcoin/UInt256.cs
Ok I think we can close this right?
good for me to close
This is to communicate which NBitcoin files or whole folders do you want other devs NOT TO TOUCH because you are working on them.
Syntax is simply, either you announce LOCK or you announce UNLOCK. The question is when to unlock, I'd say AFTER your PR is merged, otherwise it would create conflicts.
I'll start with example and the first lock:
LOCK
External\NBitcoin\Protocol\Node*.cs
except forNodesGroup.cs