SI-6017 Scaladoc's Index should be case-sensitive
Forgot to cherry-pick the .check file
There is no "letters" method in this branch
SI-4976 Scaladoc: Add a source link to package objects
SI-6853 changed private method remove to be tail recursive.
Operations += and -= on mutable.ListMap rely on the private method remove to perform. This methods was implemented using recursion, but it was not tail recursive. When the ListMap got too big the += caused a StackOverflowError.
Revert "SI-6601 Publicise derived value contstructor after pickler"

This reverts commit b07228aebe7aa620af45a681ef60d945ffc65665.

The remedy was far worse than the disease:

    % cat sandbox/test.scala
    class V private (val a: Any) extends AnyVal

    % RUNNER=scalac scala-hash b07228aebe sandbox/test.scala
    [info] b07228aebe => /Users/jason/usr/scala-v2.10.0-256-gb07228a

    % scala-hash b07228aebe
    [info] b07228aebe => /Users/jason/usr/scala-v2.10.0-256-gb07228a
    Welcome to Scala version 2.10.1-20130116-230935-b07228aebe (Java HotSpot(TM) 64-Bit Server VM, Java 1.6.0_27).
    Type in expressions to have them evaluated.
    Type :help for more information.

    scala> def foo(v: V) = v.a == v.a
    exception when typing v.a().==(v.a())/class scala.reflect.internal.Trees$Apply
    constructor V in class V cannot be accessed in object $iw in file <console>
    scala.reflect.internal.Types$TypeError: constructor V in class V cannot be accessed in object $iw
[backport] Fix for SI-6206, inconsistency with apply.

Squashed commit of the following:

commit f6bbf85150cfd7e461989ec1d6765ff4b4aeba51
Author: Paul Phillips <paulp@improving.org>
Date:   Mon Oct 1 09:10:45 2012 -0700

    Fix for SI-6206, inconsistency with apply.

    The code part of this patch is 100% written by retronym, who
    apparently has higher standards than I do because I found it just
    lying around in his repository. I think I'll go pick through his
    trash and see if he's throwing away any perfectly good muffins.

    I made the test case more exciting so as to feel useful.
    (cherry picked from commit 267650cf9c3b07e360a59f3c5b70b37fea9de453)
[backport] SI-2968 Fix brace healing for `^case (class|object) {`

Squashed commit of the following:

commit 24828531f62ce05402c96c04d7096e82d5f4e3bf
Author: Jason Zaugg <jzaugg@gmail.com>
Date:   Sun Oct 21 23:34:35 2012 +0200

    SI-2968 Fix brace healing for `^case (class|object) {`

    The scanner coalesces the pair of tokens into CASEOBJECT or
    CASECLASS, but fails to set `offset` back to the start of `case`.
    Brace healing is then unable to correctly guess the location of
    the missing brace.

    This commit resets `offset` and `lastOffset`, as though
    caseobject were a single keyword. Only the former was neccessary
    to fix this bug; I haven't found a test that shows the need for
    the latter.
    (cherry picked from commit cbad218dba47d49a39897b86d467c384538fdd53)
A test case to guide the eventual fix for SI-6601.

This demonstrates the need for the reversion in the
previous commit.
Move a test from pos to run to highlight bytecode deficiencies.

We'll address them in subsequent commits.
[backport] SI-5378, unsoundness with type bounds in refinements.

As the comment says:

Not enough to look for abstract types; have to recursively check
the bounds of each abstract type for more abstract types. Almost
certainly there are other exploitable type soundness bugs which
can be seen by bounding a type parameter by an abstract type which
itself is bounded by an abstract type.

SPECIAL: BUY ONE UNSOUNDNESS, GET ONE FREE

In refinement types, only the first parameter list of methods
was being analyzed for unsound uses of abstract types. Second
parameter list and beyond had free unsoundness reign. That bug
as well is fixed here.
SI-5313 Do not eliminate stores that potentially wipe referenes

Storing to local variables of reference or array type is indirectly
observable because it potentially allows gc to collect an object. So
this commit makes DeadCodeElimination mark a store necessary if it
assigns to a local that potentially stored by a previous necessary store.
[backport] SI-6301 / SI-6572 specialization regressions

Squashed commit of the following:

commit a3680be29ccd5314c5d027d473b37940eaecd530
Author: Paul Phillips <paulp@improving.org>
Date:   Fri Aug 31 10:20:16 2012 -0700

    Actual fix for SI-6301, specialized crasher.

    This means the workaround in the previous commit is no
    longer reached, but it should remain where it is as a much
    needed layer of robustness/useful error reporting.

    Conflicts:
    	src/compiler/scala/tools/nsc/transform/SpecializeTypes.scala
    	src/compiler/scala/tools/nsc/typechecker/Duplicators.scala

commit f4c45ae204ce3ff3c16b19cab266d0b6515b6e0f
Author: Paul Phillips <paulp@improving.org>
Date:   Fri Aug 31 10:49:24 2012 -0700

    Rewrite of GenICode adapt.

    Started for debuggability, stayed for clarify/performance.

    Conflicts:
    	src/compiler/scala/tools/nsc/backend/icode/GenICode.scala

commit 74842f72a0af485e5def796f777f7003f969d75b
Author: Paul Phillips <paulp@improving.org>
Date:   Fri Aug 31 08:45:34 2012 -0700

    Workaround for SI-6301, @specialize crasher.

    SpecializeTypes is generating symbols with overloaded types
    which then proceed to crash in CleanUp or GenICode.  Until I
    or someone works out why that is, take a look in case the
    overload is easily disambiguated by the argument list arity,
    in which case warn and proceed.
SI-6572 Test case, originally fixed in a3680be.

That fix has now been backported to 2.10.x in the
previous commit. This commit should be be merged
to master.
SI-6963 Add version to -Xmigration

Adds an optional version parameter to the -Xmigration compiler setting.
Doing -Xmigration without version number behaves as it used to by
dumping every possible migration warning.

This commit adds a ScalaVersion class (plus ancillary stuff), and a
ScalaVersionSetting.
Test case for SI-7009.

The next commit fixes the problem itself and it's easier to see
in diff what's being fixed exactly.
SI-2418, remove restriction on final vars.

[backport]
The original fix for SI-2418 excluded final vars entirely, but
the problem was not final vars per se, but the emission of ACC_FINAL
in combination with ACC_VOLATILE.  Since vars never get ACC_FINAL
now, this is no longer an issue.
SI-4729, overriding java varargs in scala.

[backport]
This was a bad interaction between anonymous subclasses
and bridge methods.

  new Foo { override def bar = 5 }

Scala figures it can mark "bar" private since hey, what's
the difference.  The problem is that if it was overriding a
java-defined varargs method in scala, the bridge method
logic says "Oh, it's private? Then you don't need a varargs
bridge." Hey scalac, you're the one that made me private!
You made me like this! You!

Conflicts:
	src/compiler/scala/tools/nsc/typechecker/RefChecks.scala
SI-5130, precision disappearing from refinement.

[backport]
Remove some code, win a prize.
SI-5353, imperfect error message.

[backport]
The fix of course is a perfect error message.