logstash-filter-delta 1.1.0 → 1.1.1

data/vendor/bundle/jruby/2.2.0/gems/sinatra-1.4.7/CONTRIBUTING.md

@@ -1,100 +0,0 @@
-# Contribute
-
-Want to show Sinatra some love? Help out by contributing!
-
-## Found a bug?
-
-Log it in our [issue tracker][ghi] or send a note to the [mailing list][ml].
-Be sure to include all relevant information, like the versions of Sinatra and
-Ruby you're using. A [gist](http://gist.github.com/) of the code that caused
-the issue as well as any error messages are also very helpful.
-
-## Need help?
-
-The [Sinatra mailing list][ml] has over 900 subscribers, many of which are happy
-to help out newbies or talk about potential feature additions. You can also
-drop by the [#sinatra](irc://chat.freenode.net/#sinatra) channel on
-[irc.freenode.net](http://freenode.net).
-
-## Have a patch?
-
-Bugs and feature requests that include patches are much more likely to
-get attention. Here are some guidelines that will help ensure your patch
-can be applied as quickly as possible:
-
-1. **Use [Git](http://git-scm.com) and [GitHub](http://github.com):**
-   The easiest way to get setup is to fork the
-   [sinatra/sinatra repo](http://github.com/sinatra/sinatra/).
-   Or, the [sinatra.github.com repo](http://github.com/sinatra/sinatra.github.com/),
-   if the patch is doc related.
-
-2. **Write unit tests:** If you add or modify functionality, it must
-   include unit tests. If you don't write tests, we have to, and this
-   can hold up acceptance of the patch.
-
-3. **Mind the `README`:** If the patch adds or modifies a major feature,
-   modify the `README.md` file to reflect that. Again, if you don't
-   update the `README`, we have to, and this holds up acceptance.
-
-4. **Update the change log (`CHANGELOG.md`):** The change log helps give an
-   overview of the changes that go into each release, and gives credit
-   where credit is due. We make sure that the change log is up to date
-   before each release, and we always appreciate it when people make
-   it easier to get the release out the door.
-
-5. **Push it:** Once you're ready, push your changes to a topic branch
-   and add a note to the ticket with the URL to your branch. Or, say
-   something like, "you can find the patch on johndoe/foobranch". We also
-   gladly accept GitHub [pull requests](http://help.github.com/pull-requests/).
-
-__NOTE:__ _We will take whatever we can get._ If you prefer to attach diffs in
-emails to the mailing list, that's fine; but do know that _someone_ will need
-to take the diff through the process described above and this can hold things
-up considerably.
-
-## Want to write docs?
-
-The process for contributing to Sinatra's website, documentation or the book
-is the same as contributing code. We use Git for versions control and GitHub to
-track patch requests.
-
-* [The sinatra.github.com repo](http://github.com/sinatra/sinatra.github.com/)
-  is where the website sources are managed. There are almost always people in
-  `#sinatra` that are happy to discuss, apply, and publish website patches.
-
-* [The Book](http://sinatra-book.gittr.com/) has its own [Git
-  repository](http://github.com/sinatra/sinatra-book/) and build process but is
-  managed the same as the website and project codebase.
-
-* [Sinatra Recipes](http://recipes.sinatrarb.com/) is a community
-  project where anyone is free to contribute ideas, recipes and tutorials. Which
-  also has its own [Git repository](http://github.com/sinatra/sinatra-recipes).
-
-* [The Introduction](http://www.sinatrarb.com/intro.html) is generated from
-  Sinatra's [README file](http://github.com/sinatra/sinatra/blob/master/README.md).
-
-* If you want to help translating the documentation, the README is already
-  available in
-  [Japanese](http://github.com/sinatra/sinatra/blob/master/README.ja.md),
-  [German](http://github.com/sinatra/sinatra/blob/master/README.de.md),
-  [Chinese](https://github.com/sinatra/sinatra/blob/master/README.zh.md),
-  [Russian](https://github.com/sinatra/sinatra/blob/master/README.ru.md),
-  [European](https://github.com/sinatra/sinatra/blob/master/README.pt-pt.md) and
-  [Brazilian](https://github.com/sinatra/sinatra/blob/master/README.pt-br.md)
-  Portuguese,
-  [French](https://github.com/sinatra/sinatra/blob/master/README.fr.md),
-  [Spanish](https://github.com/sinatra/sinatra/blob/master/README.es.md),
-  [Korean](https://github.com/sinatra/sinatra/blob/master/README.ko.md), and
-  [Hungarian](https://github.com/sinatra/sinatra/blob/master/README.hu.md).
-  The translations tend to fall behind the English version. Translations into
-  other languages would also be appreciated.
-
-## Looking for something to do?
-
-If you'd like to help out but aren't sure how, pick something that looks
-interesting from the [issues][ghi] list and hack on. Make sure to leave a
-comment on the ticket noting that you're investigating (a simple "Taking…" is
-fine).
-
-[ghi]: http://github.com/sinatra/sinatra/issues
-[ml]: http://groups.google.com/group/sinatrarb/topics "Sinatra Mailing List"

data/vendor/bundle/jruby/2.2.0/gems/sinatra-1.4.7/Gemfile

@@ -1,76 +0,0 @@
-# Why use bundler?
-# Well, not all development dependencies install on all rubies. Moreover, `gem
-# install sinatra --development` doesn't work, as it will also try to install
-# development dependencies of our dependencies, and those are not conflict free.
-# So, here we are, `bundle install`.
-#
-# If you have issues with a gem: `bundle install --without-coffee-script`.
-
-RUBY_ENGINE = 'ruby' unless defined? RUBY_ENGINE
-source 'https://rubygems.org' unless ENV['QUICK']
-gemspec
-
-gem 'rake'
-gem 'rack-test', '>= 0.6.2'
-gem "minitest", "~> 5.0"
-
-# Allows stuff like `tilt=1.2.2 bundle install` or `tilt=master ...`.
-# Used by the CI.
-repos  = {'tilt' => "rtomayko/tilt", 'rack' => "rack/rack"}
-
-%w[tilt rack].each do |lib|
-  dep = case ENV[lib]
-        when 'stable', nil then nil
-        when /(\d+\.)+\d+/ then "~> " + ENV[lib].sub("#{lib}-", '')
-        else {:github => repos[lib], :branch => dep}
-        end
-  gem lib, dep
-end
-
-if RUBY_ENGINE == 'jruby'
-  gem 'nokogiri', '!= 1.5.0'
-  gem 'jruby-openssl'
-  gem 'trinidad'
-end
-
-if RUBY_ENGINE == "ruby" and RUBY_VERSION > '1.9.2'
-  gem 'less', '~> 2.0'
-  gem 'therubyracer'
-  gem 'redcarpet'
-  gem 'wlang', '>= 2.0.1'
-  gem 'bluecloth'
-  gem 'rdiscount'
-  gem 'RedCloth'
-  gem 'puma'
-  gem 'net-http-server'
-  gem 'yajl-ruby'
-  gem 'nokogiri'
-  gem 'thin'
-  gem 'slim', '~> 2.0'
-  gem 'coffee-script', '>= 2.0'
-  gem 'rdoc'
-  gem 'kramdown'
-  gem 'maruku'
-  gem 'creole'
-  gem 'wikicloth'
-  gem 'markaby'
-  gem 'radius'
-  gem 'asciidoctor'
-  gem 'liquid'
-  gem 'stylus'
-  gem 'rabl'
-  gem 'builder'
-  gem 'erubis'
-  gem 'haml', '>= 3.0'
-  gem 'sass'
-end
-
-if RUBY_ENGINE == "rbx"
-  gem 'json'
-  gem 'rubysl'
-  gem 'rubysl-test-unit'
-end
-
-platforms :ruby_18, :jruby do
-  gem 'json' unless RUBY_VERSION > '1.9' # is there a jruby but 1.8 only selector?
-end

data/vendor/bundle/jruby/2.2.0/gems/sinatra-1.4.7/LICENSE

@@ -1,23 +0,0 @@
-Copyright (c) 2007, 2008, 2009 Blake Mizerany
-Copyright (c) 2010, 2011, 2012, 2013, 2014, 2015, 2016 Konstantin Haase
-
-Permission is hereby granted, free of charge, to any person
-obtaining a copy of this software and associated documentation
-files (the "Software"), to deal in the Software without
-restriction, including without limitation the rights to use,
-copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the
-Software is furnished to do so, subject to the following
-conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
-OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
-HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
-WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
-FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
-OTHER DEALINGS IN THE SOFTWARE.