Skip to content
This repository has been archived by the owner on Mar 26, 2023. It is now read-only.

Commit

Permalink
Merge pull request #194 from semaperepelitsa/readme_fix
Browse files Browse the repository at this point in the history
Fix typo in readme (wrong update script name)
  • Loading branch information
pbm committed Dec 11, 2012
2 parents bceff42 + 5407ea2 commit 91ab6a5
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.rdoc
Expand Up @@ -107,8 +107,8 @@ MagLev source tree and other files. Change to that directory, then:
run: run:
./install.sh ./install.sh
If you've already run <tt>installMaglev.sh</tt> on the machine, then you If you've already run <tt>installMaglev.sh</tt> on the machine, then you
can use the upgrade script: can use the update script:
./upgrade.sh ./update.sh


To use MagLev, you need to run <tt>install.sh</tt> at least once. After To use MagLev, you need to run <tt>install.sh</tt> at least once. After
that, every time you <tt>git pull</tt>, you need to run <tt>update.sh</tt> that, every time you <tt>git pull</tt>, you need to run <tt>update.sh</tt>
Expand All @@ -121,6 +121,6 @@ The installer/updater figures that out from the version.txt file.


You'll have all the functionality of git, but unless you create a new You'll have all the functionality of git, but unless you create a new
clone for each release, you may be unable to revert to an earlier version. clone for each release, you may be unable to revert to an earlier version.
Why? The install/upgrade script creates a new copy of the MagLev data Why? The install/update script creates a new copy of the MagLev data
repository including persistent kernel code. The scripts make one level of repository including persistent kernel code. The scripts make one level of
backup, but we are not providing migration scripts. backup, but we are not providing migration scripts.

0 comments on commit 91ab6a5

Please sign in to comment.