[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: Feature Request: Colored log

From: <SebastianUnger_at_eaton.com>
Date: 2006-09-22 00:26:25 CEST

Hmm, that's right a regex on the log message actually would work for us. Our scripts already put the result of the build into the log message and if TSVN would color the line based on that, that would be exactly what I want.

With optional, I meant, that you can turn colored logs off, and then SVN wouldn't even get the tsvn:log-color rev-prop. But regex matching on the log sounds like a better way for this feature. But where would you store these regex patterns. Does tortoise already have a concept of storing config information centrally somewhere. I guess, you could store it in some properties in the repo, either a normal property on the repo root or a rev-prop on rev 1. The former has the advantage that it is versioned. But then, for exactly what revision would TSVN get that property? (Head, Last Commited of the item that the log is gotten for, ...). The latter however, is more in line with how all other tortoise settings are handled, only difference is, that it is stored centrally and thus shared by all users.

Seb

-----Original Message-----
From: Simon Large [mailto:simon@skirridsystems.co.uk]
Sent: Friday, 22 September 2006 9:48
To: users@tortoisesvn.tigris.org
Subject: Re: Feature Request: Colored log

SebastianUnger@eaton.com wrote:
> Regex' don't do the job, that I had in mind, as the scripts actually
> have to change the colour of a line, once that rev has been build.
>
> As far as speed goes, don't you already have to talk to the server to
> get the log property? I know nothing about the internals of SVN server
> comms, but I would have hoped, that you can in the same round trip get
> any and all properties you need.

No. The call we use is equivalent to svn log -v, which gets log message
and author, changed files, etc in a single call. You would need a
separate call (svn propget --revprop -rN) for *each* revision to pick up
a specific rev-prop.

> Also, I guess, if you made the feature
> optional, then the danger of people chasing you would be reduced and
> even if they track you down, you would always have the defence of "Well
> YOU turned it on, didn't you?!"

You mean there's a way to stop people reading the revprops?

> I know it's very much a nice to have feature, but for us it would be,
> well, nice to have. ;-)

The only way this could work efficiently would be for your program to
add a line to the revision's log message, which is a bit risky. In that
case you could use some sort of coding like that which is used for
*bold* and _underline_, or use a regex to pick out special information
in the same way we do for bugtraq properties. This could also be used
for colour coding revisions according to whether they are bugfixes, new
features, cleanup, etc. But it all sounds like a lot of work.

Simon

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Sep 22 00:31:08 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.