| Commit message (Collapse) | Author | Age |
|
|
|
| |
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinBase/CoordGauge/trunk@66 edbb7e70-9571-45d5-a481-0a560a9b4751
|
|
|
|
|
|
|
|
|
|
| |
conditions. But at present, few (if any?) thorns seem to actually
use it. So... add a description of the way most (all?) gauge thorns
actually work at present, so the next innocent who comes along isn't
quite so confused as I was... :)
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinBase/CoordGauge/trunk@57 edbb7e70-9571-45d5-a481-0a560a9b4751
|
|
|
|
|
|
|
| |
in \tt font, thorn names in \bf font
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinBase/CoordGauge/trunk@56 edbb7e70-9571-45d5-a481-0a560a9b4751
|
|
|
|
| |
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinBase/CoordGauge/trunk@48 edbb7e70-9571-45d5-a481-0a560a9b4751
|
|
|
|
| |
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinBase/CoordGauge/trunk@46 edbb7e70-9571-45d5-a481-0a560a9b4751
|
|
are fully functional yet.
When I have completed this stage I'll send an updated spec out with some
questions which have arisen during this process.
Please don't import anything new without checking with me first, as I want
to play games on the server copying cvs files around to preserve histories
on files which are only minimally touched.
Tom
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinBase/CoordGauge/trunk@43 edbb7e70-9571-45d5-a481-0a560a9b4751
|