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

Re: change time format of $Id$

From: Clemens Schwaighofer <cs_at_tequila.co.jp>
Date: 2005-02-09 00:57:27 CET

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/09/2005 01:43 AM, Vincent Lefevre wrote:
> On 2005-02-08 11:06:19 +0900, Clemens Schwaighofer wrote:
>
>>I ask for a change in the timeformat of the svn:keyword $Id$.
>
>
> I'm completely against a hardcoded change (I still want the current
> behavior). A configurable format would be OK for me. In this case,
> this could be more general, as I've suggested in the users ML:
>
> Then how about a new keyword, but generic (with escape sequences,
> such as those used in Mutt and the Zsh prompt)? The keyword could
> have the form: Name[Format], so that using $Name$ would expand
> Name according to the specified format. Id, Date, etc. could be
> exactly like generic keywords, but with a default format.
>
> The default format could also be configurable (at least server-side).

Yeah I agree now that Id should always stay as is (never break working
code).

A new format could be

$[name][name]...$

like

$RevAuthorDate$

that would give

$1 foo user 2005-02-09 10:30:15 +0900$

- --
[ Clemens Schwaighofer -----=====:::::~ ]
[ TBWA\ && TEQUILA\ Japan IT Group ]
[ 6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ]
[ Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343 ]
[ http://www.tequila.co.jp http://www.tbwajapan.co.jp ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCCVHnjBz/yQjBxz8RAmHQAJ9FRxz9iLarypKbxfYShPh/B10B8wCeOgov
fD+Kv1kLOSeKpUKqfoLGT3g=
=0TlT
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 9 00:58:37 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.