Cassandra branch name fix #2025
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cwilkes
approved these changes
Nov 6, 2019
cwilkes
approved these changes
Nov 6, 2019
|
@marcomicera can you sync up your PR with master? I tried to do it but managed to screw up (and then fix) the changes to CHANGES.next.md but I'm still getting complaints about rebasing. The PR looks good for the Cassandra version change and I'd like to get it commited. |
|
Sure. Doing it now. |
marcomicera
force-pushed
the
fix_cassandra_branch_name
branch
from
a302e43
to
781b164
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Apache Cassandra does not have a
'cassandra-2.1.10'branch anymore. This causes thisgit checkoutcommand to fail:PerfKitBenchmarker/perfkitbenchmarker/linux_packages/cassandra.py
Lines 83 to 89 in 2df6a1c
cassandra-2.1should do the job.