GitLab

does his own commit.

* Add support for linking to the NS file that will be used, from the
  begin experiment page, when duplicating or branching an experiment.
  Ultimately we want to separate things so that user can first edit
  the NS file and then proceed to branching.

* In discussion we agreed to use the convention that a directory called
  "archive" in experiment directory, will always be saved and restored.
  This has been implemented.

* Add more of the support for branching an experiment (the archive).
  Batchexp takes a couple of new arguments:

	-c pid,eid[:tag]  or
	-c exptidx[:tag]

  The above specifies what and where to duplicate or branch. Simply
  giving pid,eid does not use the archive, but just copies right out
  of the existing experiment directory.

  Adding the -b option says to branch instead of duplicate.

by not including them in the actual pathnames to be copied with
tar/rsync.

permissions. Fixes one directory permission problem.

added in a rush and I need to take a step back and think about it.

to the archive does not exist (specifically, from the NFS tracing).

of the archive.

* The rest of the backend support for simplistic experiment duplication,
  either from an existing (current) experiment, or from a specific
  archive revision of a current or terminated experiment.

* Rework the swapmod code so that the archive is committed at the exact
  end of the swapout phase. This required adding (and moving) some code
  from swapexp to tbswap sine that is where the actual swapout/swapin
  happens during a swapmod

* Add a special directory called "archive" to the experiment
  directory, which is a place where users can store stuff they want
  saved away. This will eventually be a user defined set of
  directories, but this was good for getting the basic mechanism in
  place. Note that the when the contents of this directory are copied
  out for placement into the archive, it is an exact copy made with
  rsync.

* No longer "clean" the contents of the temporary store between
  commits of the archive. This was creating a lot of headaches, and
  was also causing the revision history to get messed up. The downside
  of this is that we have to be more careful to explicitly delete
  files that the user no longer uses. I have not solved all these
  issues yet, so in the meantime files will get left in the archive
  even if the user no longer references them.

files are being added to the archive at the correct places, but it
seems to work.

archive!

point.

going to be a lot easier!

but probably going to mangle everything again when I get back.

start,swap,swapmod,terminate.

not ready for primetime, or even late night TV.