Re: [Gnu-arch-users] automatic messages (for archive cycling etc)

[Miles Bader]

BTW, when I said:
> The advantage of a single file (or say multiple per-version files in a
> directory)

The `multiple per-version file' variant I was thinking of was the obvious
extension of the single-file idea:

   A directory, say {arch}/=update-messages/, would contain some message
   files, and tla would print all of them (`in appropriate places').  Again
   that's it, no extra rules.

It would be up to the users to name the files in the directory to avoid
conflicts, though an obvious and simple rule to do so would be (as you
mentioned) just to use the affected branch/version name as the filename for a
message about that branch.  However users could use additional or alternative
file naming conventions as they see fit (e.g., adding a `.cycled' to the end
of the version name or something).

-Miles
-- 
97% of everything is grunge