On Tue, Nov 20, 2001 at 01:36:59AM -0800, Emile Snyder wrote:
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. This is
normally not a problem, but if you have spaces in your directory or file
names, this
On Tue, 20 Nov 2001, gabriel rosenkoetter wrote:
Typically, something like (in Perl):
$_ = shift @ARGV;
my @files = split;
my $dir = $cvsroot . / . shift(@files);
would be enough to get the right stuff out on your end, but that
doesn't fix the problem you're seeing.
That is (in
On Tue, Nov 20, 2001 at 02:31:40AM -0800, Emile Snyder wrote:
On Tue, 20 Nov 2001, gabriel rosenkoetter wrote:
$_ = shift @ARGV;
my @files = split;
my $dir = $cvsroot . / . shift(@files);
That is (in spirit) exactly what log_accum does...
Well, sure, and that's not really totally
From: Emile Snyder [mailto:[EMAIL PROTECTED]]
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
From: Jerry Nairn [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 20, 2001 1:42 PM
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.
As it turns out, everything represented by %(Vsv) on the loginfo
Thanks for the pointers. I tried a different tack, which is a fairly
minimal change to the log_accum script. log_accum was doing:
@files = split (/ /, $arg);
@path = split ('/', $files[0]);
$dir = join('/', @path);
$dir .= /;
I do a little more work, and just check to see if the supposed
From: Emile Snyder [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 20, 2001 3:37 PM
Any glaring
problems anyone sees?
I don't know if you'd call it a glaring problem. There are a couple of
problems that can arise because of the way you are attempting to build the
directory name.
a) You