remove inactive branches about antidote HOT 6 CLOSED

The branches that I was using are already merged and closed - they don’t appear in the list anymore.
The status of the following branches is clear:

master

To be merged:

• causality (needs fixes for dialyzer warnings first!!!)
• sequential_log (also needs dialyzer warnings fixed, seems similar to the ones of the causality branch)
• client_api (needs fixes for dialyzer warnings first)

To be deleted:

• clock-SI
• clock-SI_v2

What about the others?

InterDCreplication
causality_plus_interdc
materializer_test
opcrdt
tests

Annette

On 01 Aug 2014, at 15:19, Alejandro Zlatko Tomsic [email protected] wrote:

We should remove the branches that have already been merged to master and the ones that we don't expect to work on any longer.
Please, each branch creator report which branches he/she knows that we can delete now.

—
Reply to this email directly or view it on GitHub.

from antidote.

Hello Annette,

are you going to delete the clock-SI ones?
I don’t know about the rest.
Best.

Alejandro Z. Tomsic
[email protected]

On Aug 4, 2014, at 18:20, bieniusa [email protected] wrote:

The branches that I was using are already merged and closed - they don’t appear in the list anymore.
The status of the following branches is clear:

master

To be merged:

• causality (needs fixes for dialyzer warnings first!!!)
• sequential_log (also needs dialyzer warnings fixed, seems similar to the ones of the causality branch)
• client_api (needs fixes for dialyzer warnings first)

To be deleted:

• clock-SI
• clock-SI_v2

What about the others?

InterDCreplication
causality_plus_interdc
materializer_test
opcrdt
tests

Annette

On 01 Aug 2014, at 15:19, Alejandro Zlatko Tomsic [email protected] wrote:

We should remove the branches that have already been merged to master and the ones that we don't expect to work on any longer.
Please, each branch creator report which branches he/she knows that we can delete now.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

from antidote.

Do we need these branches or can I nuke them?

from antidote.

Go ahead!
But for the ones where I didn’t get an answer on the status, we should first check what they actually contain...

On 09 Aug 2014, at 00:28, Christopher Meiklejohn [email protected] wrote:

Do we need these branches or can I nuke them?

—
Reply to this email directly or view it on GitHub.

from antidote.

I suggest to also delete now the sequential_log branch.
(By accident I made a commit on that one, but merged it then directly into master.)

On 09 Aug 2014, at 10:05, Annette Bieniusa [email protected] wrote:

Go ahead!
But for the ones where I didn’t get an answer on the status, we should first check what they actually contain...

On 09 Aug 2014, at 00:28, Christopher Meiklejohn [email protected] wrote:

Do we need these branches or can I nuke them?

—
Reply to this email directly or view it on GitHub.

from antidote.

I backed up the branches, and deleted them all except the ones we have to merge.

from antidote.