remotenames patches coming to the list real soon!

[Ryan McElroy]

In order to make it easier for people to participate in the development 
of Sean Farley's remotenames extension (a very diverged fork of Augie 
Fackler's remotebranches extension), and to give better visibility into 
any ongoing development of the remotenames extension, we're going to 
start using this list for remotenames patches. Don't worry, there aren't 
too many in recent days.

Thanks to Kostia Balytskyi for suggesting the idea, Sean Farley for 
supporting, and Matt Mackall for being okay with using the list this way.

More about the remotenames extension:

You can learn more about remotenames in Sean's announcement: 
https://www.mercurial-scm.org/pipermail/mercurial-devel/2015-February/066460.html 
or in the documentation on the bitbucket repo: 
https://bitbucket.org/seanfarley/hgremotenames.

At Facebook, we've found remotenames to be particularly good for large 
repositories that have a primarily centralized workflow (eg, all local 
development is eventually pushed to a single "master" repository). Note 
also that remotenames' defaults are very opinionated and most features 
are enabled by default, but it is also very configurable and allows you 
to turn most behavior changes off.

Let us know if you have any questions!

~Ryan