aspirational documentation for new repo lists

the documentation came first, which was good, because it made me think about what i wanted the repository list feature to really be.
unfortunately, that's the only change so far, so now the docs and code behavior don't match.  argh!  but soon the feature will get implemented and we'll be back in the rationality zone.

diff --git a/documentation/feisty_meow_command_reference.txt b/documentation/feisty_meow_command_reference.txt
index d885f0fab490cd87581ddd19882300e81ff64895..e67a699892e494ce1f5774307414247fce1ff670 100644 (file)
--- a/documentation/feisty_meow_command_reference.txt
+++ b/documentation/feisty_meow_command_reference.txt
@@ -99,10 +99,19 @@ then operates on those names.
   changes that could cause problems later.
 
 ========
-the next suite of commands uses the REPOSITORY_LIST environment variable as
-the set of revision controlled folders to operate on.  the feisty meow scripts
-automatically add the feisty meow top-level (the apex) to this list to ensure
-that updates are received when available.
+the next suite of commands uses the REPOSITORY_LIST* environment variables
+as the set of revision-controlled folders to operate on:
+
+  REPOSITORY_LIST_TO_PULL => the set of version-controlled folders that the user
+  wants updated when checkouts occur (e.g. the "getem" and "puffer" functions,
+  or the first phase of the "checkin" function).
+
+  REPOSITORY_LIST_TO_COMMIT => the set of version-controlled folders that the
+  user wants to be checked in when commits occur (e.g. the second phase of
+  the "checkin" function).
+
+the feisty meow scripts automatically add the feisty meow top-level (the
+apex) to the pull list to ensure that updates are received when available.
 ========
 
   getem: