New patches:

[unrevert
anonymous**20090917102004] hunk ./Changelog 1
-Changes since 2999.1.0.2
-========================
+Changes in 2999.5.1.0
+=====================
 
 A major re-write occured; these are the highlights:
 
hunk ./Changelog 37
   uses "from" and "to" avoid ambiguity; the various Attribute values
   still follow upstream usage.
 
-Changes since 2999.1.0.1
-========================
+Changes in 2999.1.0.2
+=====================
 
 * Fix a bug spotted by Srihari Ramanathan where Color values were
   double-quoted.
hunk ./Changelog 43
 
-Changes since 2999.1.0.0
-========================
+Changes in 2999.1.0.1
+=====================
 
 * The Color Attribute should take [Color], not just a single Color.
 
hunk ./Changelog 48
-Changes since 2999.0.0.0
-========================
+Changes in 2999.1.0.0
+=====================
 
 * Stop using Either for composite Attributes and use a custom type:
   this avoids problems with the Show instance.
hunk ./Changelog 54
 
-Changes since 2009.5.1
-======================
+Changes in 2999.0.0.0
+=====================
 
 * Fixed a bug where the Show instance and read function for DotEdge
   had the from/to nodes the wrong way round.  This was not immediately
hunk ./Changelog 82
 * Follow the PVP rather than using dates for versions:
   http://www.haskell.org/haskellwiki/Package_versioning_policy
 
-Changes since 2008.9.20:
-========================
+Changes in 2009.5.1
+===================
 
 * Support polyparse >= 1.1 (as opposed to < 1.3)
 
hunk ./Changelog 99
 
 * Improved Haddock documentation.
 
-Changes since 2008.9.6
-======================
+Changes in 2008.9.20
+====================
 
 * Differentiate between undirected and directed graphs (previously
   only directed graphs were supported).
hunk ./graphviz.cabal 2
 Name:               graphviz
-Version:            2999.5.0.0
+Version:            2999.5.1.0
 Stability:          Beta
 Synopsis:           GraphViz bindings for Haskell.
 Description:        Provides convenient functions to convert FGL

Context:

[For Double values that are actually "integral", print them as an integer.
Ivan.Miljenovic@gmail.com**20090917101427
 Ignore-this: 4f9aa93066095f4491637fd5242b671d
 This seems to match how GraphViz does it (e.g. print "2" rather than
 "2.0").
] 
[Hopefully fix the graphvizWithHandle bug
Ivan.Miljenovic@gmail.com**20090917085520
 Ignore-this: 5cc11514205b9afbb89d14b0f48fa886
 Thanks to Nikolas Mayr for pointing out where the error was: I thought
 it was with runGraphvizCommand, but he found it was in the various
 graphToGraph-style functions.
 
 Not going to declare this closed yet; will wait for a while and see.
] 
[Don't use commit for parseSigned
Ivan.Miljenovic@gmail.com**20090917084932
 Ignore-this: 1bd58544a439ba65577b25bdf6e8f6ae
 This resulted in cases for Point such as "-1.8,2.3" where intDblPoint
 would try parsing it as Int first, get "-1" and then complain that
 ".8" wasn't a comma.  Because of commit, it couldn't backtrack and try
 the next parser from `onFail` (and eventually reach the correct one).
] 
[The Dot specs lie: Exponents _are_ allowed in Doubles
Ivan.Miljenovic@gmail.com**20090917080051
 Ignore-this: 972516ba1932d85bb3a85726bfdd617a
 At the moment, this might break if numbers like 10e30 are allowed, as
 parseFloat assumes a decimal point does exist...
] 
[Haddock fixup
Ivan.Miljenovic@gmail.com**20090917071912
 Ignore-this: 4f8eccc85c469d4a3c7ff8450adb1820
] 
[-Wall fixup
Ivan.Miljenovic@gmail.com**20090917071638
 Ignore-this: 439b9e2db967762ac81416ddb9956bb1
] 
[Use the new parseComma parser
Ivan.Miljenovic@gmail.com**20090917064249
 Ignore-this: b22e0ca307006c0ac170f05da7ad3cfd
] 
[Add support for parsing out comments and multiline strings
Ivan.Miljenovic@gmail.com**20090917064134
 Ignore-this: 1f971f39c7e6f56b5fa0f047a98a2b2c
] 
[Clean up Parsing
Ivan.Miljenovic@gmail.com**20090917041316
 Ignore-this: fa2f8277c9f52326d332a91a633b144a
 Add sections to haddock docs; abstract out parts of some functions.
] 
[Some Attribute values allowed quotes for parseUnqt... fix this
Ivan.Miljenovic@gmail.com**20090916131258
 Ignore-this: 7881f2185830851f97bd47111aee6c43
] 
[Fix up parsing of Point values
Ivan.Miljenovic@gmail.com**20090916091046
 Ignore-this: 3485148ea4f212b911f8a91dadad5191
 When there's a point like "2,3.0", care must be taken so that it isn't
 parsed as Int,Int with trailing String (which then ruins the next
 parse).  Can't just swap parsing order, because then "2,3" will be
 parsed as Double,Double.
] 
[Fix up number parsing
Ivan.Miljenovic@gmail.com**20090916090935
 Ignore-this: 37cc31896d0073cb80f42cee96be86e3
 Can now parse numbers like ".02" properly.  Also provide
 parseStrictFloat for when a number with decimals definitely has to be parsed.
] 
[Fix up parsing of Splines
Ivan.Miljenovic@gmail.com**20090916061959
 Ignore-this: b67e1e3cc729e2530b2ba6a2dda65009
 Don't want quotes around the optional points that are parsed
] 
[TAG 2999.5.0.0
Ivan.Miljenovic@gmail.com**20090909094023
 Ignore-this: b0bd024c8f604cd404cd61a83326cb0c
] 
Patch bundle hash:
3ba2c1864c2ba3ffee32a9e4bcffc2fcfb584428