The output from that command is the name of a file which you must now
edit. Initially it contains:

Summary:
Keywords:

You should fill out this file just like an email message. Add a short
description of the revision in the Summary:
field, and a full
description in the body. Just as in email, the body must be separated
from the headers by a blank line. When you're done, the log might look
like this:

Summary: initial import
Keywords:
This is the initial import of `hello-world', the killer app
that will propel our new .com company to a successful IPO.

Usage Note for vi Fans: The default filename of log messages starts
with the character +
. vi
is a non-standard program in the sense
that it treats arguments starting with +
as options rather than
ordinary arguments. Therefore, you should be sure to type the
filename for vi
starting with ./
, as in:

% vi ./++log.hello-world--mainline--0.1--lord@emf.net--2003-example

or you could simply:

% vi `tla make-log`

Storing the First Revision in the Archive

Finally, we can ask arch
to add our source to the archive:

% tla import
[....]

Note: If you have received an error along the lines of
These
apparent source files lack inventory ids
, please reread
Inventory Ids for Source and either add each file or
change the id-tagging-method to names.

We can observe the side effects of that command in a few ways.

For one thing, we can ask arch
what revisions exist in the archive
for our project:

You should notice that the tar file does not include every file from
your project tree. Specifically, it contains those files that are
listed by:

% cd ~/wd/hello-world
% tla inventory --source --both --all
[....]

Finally, if you poke around in the {arch}
subdirectory of your
project tree, you'll see two new items:

% ls
++default-version =tagging-method
++pristine-trees hello-world

The directory ++pristine-trees
contains (at some depth) a copy of
the tree you just imported. This is a cached copy used by other
arch
commands. (Note: In future releases of arch
, it is likely
that the ++pristine-trees
subdirectory will be replaced by a
different mechanism.)

If you dig around in the hello-world
(patch log) directory, you
can find a local copy of the log file for the revision you just
created (with extra headers added to that log file).