Re: Possible way to support $Log$

John Peacock wrote:
...
Lots about logs
...
I like the B1 solution most:
> B1) $Log[4]$ means include the last 4 history records;

How about embedding the log between $LogN$ and $LogEnd$ tags
where N is the number of log entries to include. If N is omitted, all
log entries are shown.
There also has to be a file extension specific line comment property
(let's call it LC) to make everything work.

Assume that LC = '//' and you want your last five log entries in the
file's header. So you just insert:

// $Log5$

and commit. The next person updating the file will receive

// $Log5:
// My
// last
// five
// log
// entries
// $LogEnd$

Upon a commit everything following the $LogN: and including $LogEnd$ is
dumped and $LogN: becomes $LogN$ again. The colon indicates, that the
$LogN$ is expanded.

How about that?

Cheers
-Lübbe

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 21 10:28:36 2004