Index: includes/bootstrap.inc
===================================================================
RCS file: /cvs/drupal/drupal/includes/bootstrap.inc,v
retrieving revision 1.462
diff -u -r1.462 bootstrap.inc
--- includes/bootstrap.inc	5 Jan 2011 06:17:58 -0000	1.462
+++ includes/bootstrap.inc	7 Jan 2011 10:41:38 -0000
@@ -354,15 +354,16 @@
  * $sites = array(
  *   'devexample.com' => 'example.com',
  *   'localhost.example' => 'example.com',
+ *   '8080.localhost' => 'example.com',
  * );
  *
  * The above array will cause Drupal to look for a directory named
  * "example.com" in the sites directory whenever a request comes from
- * "example.com", "devexample.com", or "localhost/example". That is useful
- * on development servers, where the domain name may not be the same as the
- * domain of the live server. Since Drupal stores file paths into the database
- * (files, system table, etc.) this will ensure the paths are correct while
- * accessed on development servers.
+ * "example.com", "devexample.com", "localhost/example", or "localhost:8080".
+ * That is useful on development servers, where the domain name may not be 
+ * the same as the domain of the live server. Since Drupal stores file paths
+ * into the database (files, system table, etc.) this will ensure the paths
+ * are correct while accessed on development servers.
  *
  * @param $require_settings
  *   Only configuration directories with an existing settings.php file
Index: sites/example.sites.php
===================================================================
RCS file: /cvs/drupal/drupal/sites/example.sites.php,v
retrieving revision 1.3
diff -u -r1.3 example.sites.php
--- sites/example.sites.php	15 Apr 2010 12:01:28 -0000	1.3
+++ sites/example.sites.php	7 Jan 2011 10:41:28 -0000
@@ -19,15 +19,16 @@
  * $sites = array(
  *   'devexample.com' => 'example.com',
  *   'localhost.example' => 'example.com',
+ *   '8080.localhost' => 'example.com',
  * );
  *
  * The above array will cause Drupal to look for a directory named
  * "example.com" in the sites directory whenever a request comes from
- * "example.com", "devexample.com", or "localhost/example". That is useful
- * on development servers, where the domain name may not be the same as the
- * domain of the live server. Since Drupal stores file paths into the database
- * (files, system table, etc.) this will ensure the paths are correct while
- * accessed on development servers.
+ * "example.com", "devexample.com", "localhost/example", or "localhost:8080".
+ * That is useful on development servers, where the domain name may not be 
+ * the same as the domain of the live server. Since Drupal stores file paths
+ * into the database (files, system table, etc.) this will ensure the paths
+ * are correct while accessed on development servers.
  *
  * To use this file, copy and rename it such that its path plus filename is
  * 'sites/sites.php'. If you don't need to use multi-site directory aliasing,