[Top][All Lists]

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

Re: loginfo %s question

From: gabriel rosenkoetter
Subject: Re: loginfo %s question
Date: Tue, 20 Nov 2001 05:37:50 -0500
User-agent: Mutt/1.2.5i

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 sufficient by itself, but
it's the reasoning behind having that stuff space-separated, as near
as I can tell.

> :)  Ah if only it were so easy...

Well, how about passing things through a script of your own that
re-groks stuff (adding \s before spaces and making everything comma
separated) before passing it off to a (modified, to deal with comma
separate) log_accum, then? (Should be easy to do the latter. Just
split on ',' rather than the default '[whitespace]'.)

(Is that off the wall for some important reason I'm missing at 5:30
am, local time?)

> Yeah.  It's a case of making the tool fit the current situation.  We've
> got some Windows only code under cvs control where the initial projects
> were created with normal windows directory names (ie some had spaces).
> Till now it didn't matter; only ever dealt with the projects on windows.  
> But the loginfo scripts run on the server, so they've gotta handle the
> naming in our current projects.  <dream>Someday maybe I'll get to clean up
> the repository. </dream>

Yep. That's a drag. Sorry. :^>

       ~ g r @

Attachment: pgpPX0L46dPUY.pgp
Description: PGP signature

reply via email to

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