Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates
 209.85.215.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAO5xsd087guMwv5QC+pj6tNbooLiqerk2YtMdEbJq1DEwrthSQ@mail.gmail.com>
References: <0ED62951-C003-4265-B3C0-6D99BE130AD0@me.com>
 <CAO5xsd087guMwv5QC+pj6tNbooLiqerk2YtMdEbJq1DEwrthSQ@mail.gmail.com>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Fri, 19 Aug 2011 14:27:21 -0500
Message-ID: 
 <CALdd-zh3oYxZSkSYYmhFjhdGDS3hwdJQpzg3=aBCDkdXkM05NA@mail.gmail.com>
Subject: Re: How can I patch a single issue
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I think this is what you want:
https://github.com/stuhood/cassandra/tree/file-format-and-promotion

On Fri, Aug 19, 2011 at 1:28 PM, Peter Schuller
<peter.schuller@infidyne.com> wrote:
>> https://issues.apache.org/jira/browse/CASSANDRA-674
>> But when I downloaded the patch file I can't find the correct trunk to
>> patch...
>
> Check it out from git (or svn) and apply to trunk. I'm not sure
> whether it still applies cleanly; given the size of the patch I
> wouldn't be surprised if some rebasing is necessary. You might try a
> trunk from further back in time (around the time Stu submitted the
> patch).
>
> I'm not quite sure what you're actual problem is though, if it's
> source code access then the easiest route is probably to check it out
> from https://github.com/apache/cassandra
>
> --
> / Peter Schuller (@scode on twitter)
>


-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com