commit/MacHg: 9 new changesets

[Bitbucket]

9 new changesets in MacHg:

http://bitbucket.org/jfh/machg/changeset/2e90e4216350/
changeset: 2e90e4216350
user: dak180
date: 2011-02-13 02:28:49
summary: Initial neatening of the xcode project.
affected #: 1 file (-1 bytes)

http://bitbucket.org/jfh/machg/changeset/01d8c233aef9/
changeset: 01d8c233aef9
user: dak180
date: 2011-02-13 02:56:25
summary: Clean up some paths in the project.
affected #: 1 file (-1 bytes)

http://bitbucket.org/jfh/machg/changeset/69f1d574fa84/
changeset: 69f1d574fa84
user: dak180
date: 2011-02-14 05:48:50
summary: Externalize the build settings.
affected #: 5 files (-1 bytes)

http://bitbucket.org/jfh/machg/changeset/3e7bc64209bd/
changeset: 3e7bc64209bd
user: dak180
date: 2011-02-14 05:58:32
summary: Externalize the BuildHashKey script.
affected #: 2 files (-1 bytes)

http://bitbucket.org/jfh/machg/changeset/926b686ce04c/
changeset: 926b686ce04c
user: dak180
date: 2011-02-15 06:24:52
summary: Make sure that the correct GC settings are used in all builds.
affected #: 2 files (-1 bytes)

http://bitbucket.org/jfh/machg/changeset/d62837a8e29b/
changeset: d62837a8e29b
user: dak180
date: 2011-02-16 00:28:28
summary: Compile with LLVM-GCC since Clang seems to result in an unusable binary.
affected #: 2 files (-1 bytes)

http://bitbucket.org/jfh/machg/changeset/1c3f4b9a2f84/
changeset: 1c3f4b9a2f84
user: dak180
date: 2011-09-15 16:27:27
summary: Get rid of build settings that do not do anything.
affected #: 1 file (-1 bytes)

http://bitbucket.org/jfh/machg/changeset/bc9f1a5964c4/
changeset: bc9f1a5964c4
user: jfh
date: 2011-09-18 03:05:26
summary: Added tag latestRelease for changeset 1c3f4b9a2f84
affected #: 1 file (-1 bytes)

http://bitbucket.org/jfh/machg/changeset/130e39c09c2e/
changeset: 130e39c09c2e
user: jfh
date: 2011-09-18 03:06:09
summary: Added tag release0.9.24 for changeset 1c3f4b9a2f84
affected #: 1 file (-1 bytes)

Repository URL: https://bitbucket.org/jfh/machg/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.