Re: [Help-gnu-arch] Help composing a sample session

[Thomas Lord]

Hi Eric,

I'm not up to speed on the very latest behavior of tla, but
I can give you general guidance about the confusion people
used to have around this.   You have to forgive where my
memory is sketchy on some details that can easily be cross-checked
with the code.

As I recall, a valid log file is vaguely RFC822-ish in the sense that
it has headers, then a line with nothing but a newline, then a body.

I *think* the body is optional, but the blank line before the
body is not -- check the code.   When I first wrote that part, I tried
to be conservative in the sense of making it a little harder to accidentally
commit with a log file other than the one you meant.

So, your "edit the log file" step *might* be messing up the syntax
of the log file in such a way that it doesn't pass muster.   Take
a peek at the code for certain picture, though.   Hopefully these
suggestions will make the code easier to read.

Thanks,
-t



Eric S. Raymond wrote:
> I'm trying to write a sample Arch session for a survey paper I'm
> working on, and failing.
>
> Here's my sequence of commands;
>
>   # Clear all arch state
>   rm -fr {arch} {archives} ~/.arch-params/ .arch-ids foo.txt address@hidden
>
>   tla my-id "Eric S. Raymond <address@hidden>"
>   mkdir {archives}
>   tla make-archive address@hidden {archives}/2007-example
>   tla my-default-archive address@hidden
>   tla archives
>   tla whereis-archive address@hidden
>   tla archive-setup example--trunk--0.1
>   tla categories
>   tla branches example
>   tla versions example--trunk
>   tla init-tree example--trunk--0.1
>   echo "This is a one-liner file." >foo.txt
>   tla add foo.txt
>   tla make-log
>
> The last command echoes this:
>
> address@hidden
>
> I then edit the log file, 
>
> The problem cones when I try to commit:
>
> commit: tree has no patch log entries for version
>     tree: /home/esr/public_html/writings/version-control
>     version:address@hidden/example--trunk--0.1
>
> This log message is actually missing its trailing \n, so my next
> shell prompt is run on to it.
>
> What am I doing wrong here?
>