The entire svn revision history was preserved with the change, so doing
svn co -r917130 http://svn.apache.org/repos/asf/thrift/trunk/
would suffice.
Todd
On Tue, Nov 9, 2010 at 1:20 PM, Gary Dusbabek wrote:
> No, that's the one. Thrift has graduated since then, which means
> their svn url ch
http://jline.sourceforge.net/
On Mon, Aug 9, 2010 at 8:54 PM, S Ahmed wrote:
> Hi,
>
> Curious if the command line tool (cassandra-cli) uses some existing lib to
> give it base functionality like tab-autocomplete etc.
>
You should create a ticket in JIRA, and attach the patch to it. The process
is described here: http://wiki.apache.org/cassandra/HowToContribute
On Sat, Jun 26, 2010 at 5:47 PM, Marty Greenia wrote:
> Hello all,
>
> In browsing through the code, I spent some time fixing up the whitespace --
> most
If you feel you have a solid understanding of the code, you might want to
browse some of the open tickets and identify those which seem doable to you.
That's really the best way to get started, IMO.
https://issues.apache.org/jira/browse/CASSANDRA
The lack of comments does present a challenge to n
+1
On Mon, May 24, 2010 at 2:02 PM, Eric Evans wrote:
>
> As promised, here is the 0.6.2 vote.
>
> The list of changes from 0.6.1 is longer than I'd have liked, so it
> would be great if everyone can give this one an extra-special once over.
> Don't be afraid to drop a veto if you spot any regre
I'm unfamiliar with the process, and I'm not sure if input from plain
contributors is considered, but I can't think of anyone more deserving of
committer status. When I implemented the code to convert the configuration
file to YAML, Stu gave me plenty of extra feedback and carefully pointed out
som
Hi Liangzhao,
For some reason, Eclipse believes there are access restrictions imposed on
that class. After doing some googling, it seems the most common solution is
to simply reload the standard Java APIs. To do this:
1) go to your build path settings for your cassandra project in Eclipse, and
un
