[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: loginfo %s question

From: Jerry Nairn
Subject: RE: loginfo %s question
Date: Tue, 20 Nov 2001 13:42:11 -0800

> From: Emile Snyder [mailto:address@hidden
> Sent: Tuesday, November 20, 2001 1:37 AM

> I'm messing with the contrib scripts commit_prep and 
> log_accum to try to
> get one-email-per-commit notifications rather than one per directory

Some fun.

> However, %s doesn't seem to be just the file name, as the 
> default loginfo
> comment indicates, but rather "directory file", ie. with a 
> space.

As someone else pointed out, and as it says in the manual "the first token
is the repository directory." The %s is just the file name or names, but it
will always be preceded by the directory name. If you've been looking at
log_accum and commit_prep, you should have seen that this repository
directory name is important.

> This is
> normally not a problem, but if you have spaces in your 
> directory or file
> names, this makes it impossible to parse out the argument passed to
> log_accum.

I had to go through exactly what you're doing at a previous employer who had
many spaces in file and directory names. Unfortunately, I no longer have
access to that work. I'll write to someone I know there and see if I can get
their modified scripts. Probably not.
What I had to do was to put in a lot of quoting which wasn't there before,
and use %(Vsv) as the format string in loginfo. This makes it possible to
parse <Old Version #><comma><filename><comma><New Version #>.
Much easier.

> If I have a module cvstest, with the following files:
> cvstest/dira/filea
> cvstest/space dir/fileb
> cvstest/space dir/space file

Maybe directory names with spaces were still a problem. It seems to me they
would be. I don't remember a solution to that problem.
I'll let you know if I recover my earlier work.
Good luck,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]