mail 2.7.0.rc1 → 2.7.0.rc2

data/CONTRIBUTING.md

@@ -1,60 +0,0 @@
-Contributing to Mail
-====================
-
-Hi there, I welcome pull requests!  Here are some thoughts on how to get your
-pull request merged quickly:
-
-1. Check the Reference RFCs, they are in the References directory, so no excuses.
-2. Check for a ticket on GitHub, maybe someone else has the problem too
-3. Make a fork of my GitHub repository
-4. Run the specs. We only take pull requests with passing tests, and it's great
-   to know that you have a clean slate: `bundle && bundle exec rake`
-5. Add a spec for your change. Only refactoring and documentation changes
-   require no new specs. If you are adding functionality or fixing a bug, we need
-   a spec!
-6. Test the spec _at_ _least_ against MRI-1.9.3 and MRI-1.8.7
-7. Update the README if needed to reflect your change / addition
-8. Update the CHANGELOG and give yourself credit
-9. With all specs passing push your changes back to your fork
-10. Send me a pull request.
-  - If it needs any changes, please push or force push to the same branch you made the pull request from.  GitHub will just update the pull request with your changes.
-
-Note, specs that break MRI 1.8.7 or 1.9.3 will not be accepted.
-
-At this point you're waiting on us. We like to at least comment on, if not
-accept, pull requests within three business days (and, typically, one business
-day). We may suggest some changes or improvements or alternatives.
-
-Some things that will increase the chance that your pull request is accepted,
-taken straight from the Ruby on Rails guide:
-
-* Tell me you have tested it against more than one version of Ruby, RVM is great for
-  this. I test against 7 rubies before I push into master.
-* Use good, idiomatic, structured and modular code
-* Include tests that fail without your code, and pass with it
-* Update the documentation, the surrounding one, examples elsewhere, guides,
-  whatever is affected by your contribution
-
-Syntax:
-
-* Two spaces, no tabs.
-* No trailing whitespace. Blank lines should not have any space.
-* Prefer &&/|| over and/or.
-* MyClass.my_method(my_arg) not my_method( my_arg ) or my_method my_arg.
-* a = b and not a=b.
-* Follow the conventions you see used in the source already.
-
-And in case we didn't emphasize it enough: we love specs!
-
-### Testing against mime-types versions:
-
-Use [appraisal](https://github.com/thoughtbot/appraisal) to run against all supported versions of mime-types.
-
-1. Run `(bundle check || bundle) && appraisal` so that all the 'appraised' gemfiles are bundled.
-2. Run either `appraisal rake` or `rake appraisal` to run all the tests.
-
-To run only one 'appraised' gemfile, run. e.g. `BUNDLE_GEMFILE=gemfiles/mime_types_edge.gemfile (bundle check || bundle) && rake`
-
-To change the appraisals, modify the `Appraisals` file, run `appraisal`, commit the generated gemfiles, and modify the .travis.yml matrix.
-
-To run on all rubies / gemfiles, just like TravisCI, see [WWTD](https://github.com/grosser/wwtd).

data/Dependencies.txt

@@ -1 +0,0 @@
-tlsmail: if ruby < 1.8.6... we could make it optional, or embed it in Mail

data/Gemfile

@@ -1,11 +0,0 @@
-source 'https://rubygems.org'
-
-gemspec
-
-gem 'tlsmail', '~> 0.0.1' if RUBY_VERSION <= '1.8.6'
-gem 'jruby-openssl', :platforms => :jruby
-
-gem 'rake', '< 11.0' if RUBY_VERSION < '1.9.3'
-gem 'rdoc', '< 4.3' if RUBY_VERSION < '2.0'
-
-gem 'mini_mime', :github => 'discourse/mini_mime'

data/Rakefile

@@ -1,23 +0,0 @@
-if !ENV["APPRAISAL_INITIALIZED"] && !ENV["TRAVIS"]
-  ENV['BUNDLE_GEMFILE'] ||= File.expand_path('../Gemfile', __FILE__)
-end
-require 'rubygems'
-require 'bundler/setup'
-
-require 'rake/testtask'
-require 'rspec/core/rake_task'
-
-desc "Build a gem file"
-task :build do
-  system "gem build mail.gemspec"
-end
-
-task :default => :spec
-
-RSpec::Core::RakeTask.new(:spec) do |t|
-  t.ruby_opts = '-w'
-  t.rspec_opts = %w(--backtrace --color)
-end
-
-# load custom rake tasks
-Dir["#{File.dirname(__FILE__)}/tasks/**/*.rake"].sort.each { |ext| load ext }

data/TODO.rdoc

@@ -1,9 +0,0 @@
-== Not really in any order:
-
-* Add multibyte handling to fields, if they get a multibyte string, try encoding it into 
-  UTF-8 B first, if this fails, throw an error.
-
-* Cleanup the treetop parsers......... do I _really_ need that many entrance files?
-
-* Simplify the relationship of Headers and Fields.  Doing too much of the Field work
-  in the Header class on instantiating fields.  Header should just say "Field, do it!"

data/lib/mail/multibyte/exceptions.rb

@@ -1,9 +0,0 @@
-# encoding: utf-8
-# frozen_string_literal: true
-
-module Mail #:nodoc:
-  module Multibyte #:nodoc:
-    # Raised when a problem with the encoding was found.
-    class EncodingError < StandardError; end
-  end
-end