Re: Format for 1.11.10's contrib's loginfo, used by log_accum com mit

2003-12-17 Thread vikas arora
- (on mail)

mail is scanned with InterScan

-
Kindly check while i try to add some file to the repository I am getting the
error

cvs add: in directory .:

cvs [add aborted]: there is no version here; do 'cvs checkout' first

Even If check out some module andwanted to add some file to it, the same
error is coming.does this mean that i can't explicitly add a single file
into the repository.

Regards

Vikas arora

- Original Message -
From: "vikas arora" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 10, 2003 2:33 PM
Subject: Re: Format for 1.11.10's contrib's loginfo,used by log_accum com
mit


> - (on mail)
>
> mail is scanned with InterScan
>
> -
>






> I am new user of CVS, just want to incorporate it for the source code
> management of FMBs and FMXs.Just wanted to know whether it is possible to
> check out a single file using cvs or do i need to set up the repository
> first and then only I be able to checkout the files.
>
> Regards
> Vikas
>
>
> - Original Message -
> From: "Andy Jones" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, December 10, 2003 2:23 PM
> Subject: RE: Format for 1.11.10's contrib's loginfo, used by log_accum com
> mit
>
>
> >
> > >Larry, Larry, Larry,...  Trust me. If you've never encountered
constructs
> > >like @_, my, local($wd, @files); scalars, arrays... (and btw, 'local'
is
> > >not local, 'my' is local...how cute), reading it is doable but
tediously
> > >slow.  I'm reminded of a friend's admonition in college.  He said:
> > >"Physics is easy, once you know it."
> >
> > Seconded.
> >
> > I think the readability of Perl is a subjective thing, not an objective
> > thing.  Some people find it easy, like some people find reading upside
> down
> > easy.
> >
> > Personally, when I see a Perl script, I start running...
> >
> >
> >
> >
> >
> > ___
> > Info-cvs mailing list
> > [EMAIL PROTECTED]
> > http://mail.gnu.org/mailman/listinfo/info-cvs
> >
>






> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs
>
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs


Re: Format for 1.11.10's contrib's loginfo, used by log_accum com mit

2003-12-10 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Andy Jones <[EMAIL PROTECTED]> writes:

> > Larry, Larry, Larry,...  Trust me. If you've never encountered
> > constructs like @_, my, local($wd, @files); scalars, arrays... (and
> > btw, 'local' is not local, 'my' is local...how cute), reading it is
> > doable but tediously slow.  I'm reminded of a friend's admonition in
> > college.  He said: "Physics is easy, once you know it."
> 
> Seconded.
> 
> I think the readability of Perl is a subjective thing, not an
> objective thing.  Some people find it easy, like some people find
> reading upside down easy.
> 
> Personally, when I see a Perl script, I start running...

The files in contrib are there because some folks think they are useful.

I have been programming with perl since version 3.0 was released to the
net, so I don't have any problems reading it, but I do understand what
you mean.

If you have examples for commitinfo, verifyinfo, loginfo and taginfo
scripts in some other language that you would like to contribute, by all
means feel free to do it as long as you give it some kind of copyright
license that allows it to be put into a cvs source distribution, I would
have no problems seeing examples in shell, python, tcltk, c, or whatever
other kind of language seems reasonable.

Thanks,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/1uR63x41pRYZE/gRAjsSAKDicXs0S7J5wz+4RPq8mx48y2AGowCgtZdX
Fwkjjx3WyTN5Z+QoVZcaLQo=
=6qqc
-END PGP SIGNATURE-


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs


Re: Format for 1.11.10's contrib's loginfo, used by log_accum com mit

2003-12-10 Thread Andy Jones
At 09:16 am 10/12/03, Mark D. Baushke wrote:
The files in contrib are there because some folks think they are useful.
And they *are* useful.  No doubt.  Perl is a very powerful language.  It's 
just that it's a very powerful language that some people have trouble reading.

Here I've written some scripts in TCL, but I doubt that they are useful 
enough in the general sense for me to publish them, even if I could.





___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs


Re: Format for 1.11.10's contrib's loginfo, used by log_accum com mit

2003-12-10 Thread vikas arora
- (on mail)

mail is scanned with InterScan

-
I am new user of CVS, just want to incorporate it for the source code
management of FMBs and FMXs.Just wanted to know whether it is possible to
check out a single file using cvs or do i need to set up the repository
first and then only I be able to checkout the files.

Regards
Vikas


- Original Message -
From: "Andy Jones" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 10, 2003 2:23 PM
Subject: RE: Format for 1.11.10's contrib's loginfo, used by log_accum com
mit


>
> >Larry, Larry, Larry,...  Trust me. If you've never encountered constructs
> >like @_, my, local($wd, @files); scalars, arrays... (and btw, 'local' is
> >not local, 'my' is local...how cute), reading it is doable but tediously
> >slow.  I'm reminded of a friend's admonition in college.  He said:
> >"Physics is easy, once you know it."
>
> Seconded.
>
> I think the readability of Perl is a subjective thing, not an objective
> thing.  Some people find it easy, like some people find reading upside
down
> easy.
>
> Personally, when I see a Perl script, I start running...
>
>
>
>
>
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs
>
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs


RE: Format for 1.11.10's contrib's loginfo, used by log_accum com mit

2003-12-10 Thread Andy Jones

Larry, Larry, Larry,...  Trust me. If you've never encountered constructs 
like @_, my, local($wd, @files); scalars, arrays... (and btw, 'local' is 
not local, 'my' is local...how cute), reading it is doable but tediously 
slow.  I'm reminded of a friend's admonition in college.  He said: 
"Physics is easy, once you know it."
Seconded.

I think the readability of Perl is a subjective thing, not an objective 
thing.  Some people find it easy, like some people find reading upside down 
easy.

Personally, when I see a Perl script, I start running...





___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs


Re: Format for 1.11.10's contrib's loginfo, used by log_accum com mit

2003-12-09 Thread Eric Siegerman
On Tue, Dec 09, 2003 at 05:06:37PM -0800, Peter Connolly wrote:
> General question: Is it really expected that EVERYONE that
> wants to set up and use these contrib scripts have to read
> them, understand them and retro-engineer the inputs?

Well, contrib/README doesn't mention documentation, but that's
the only part of "you're completely on your own" that it doesn't
explicitly spell out :-)

Larry, I've attached a patch to fix that (too trivial to be worth
a ChangeLog entry IMO).

--

|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
|  |  /
It must be said that they would have sounded better if the singer
wouldn't throw his fellow band members to the ground and toss the
drum kit around during songs.
- Patrick Lenneau
Index: README
===
RCS file: /cvs/ccvs/contrib/README,v
retrieving revision 1.18
diff -u -r1.18 README
--- README  21 Nov 2002 19:04:38 -  1.18
+++ README  10 Dec 2003 02:26:20 -
@@ -4,7 +4,8 @@
 contributions are really, REALLY UNSUPPORTED.  In fact, we probably
 don't even know what some of them really do.  We certainly do not
 guarantee to have tried them, or ported them to work with this CVS
-distribution.  If you have questions, your best bet is to contact the
+distribution.  Their documentation might be lousy, nonexistent, or just
+plain wrong.  If you have questions, your best bet is to contact the
 original author, but you should not necessarily expect a reply, since
 the author may not be available at the address given.
 
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs


Re: Format for 1.11.10's contrib's loginfo, used by log_accum com

2003-12-09 Thread Larry Jones
Peter Connolly writes:
> 
> I've tried that and when I commit, I get the following messages:
> 
>Processing log script arguments...
>Mailing the commit message to (from [EMAIL PROTECTED])
>No recipient addresses found in header
> 
> which I guess means that $mail_to and its progenitor $addr_list in the
>  subroutine are not being set properlybut no
> hints as to how to format those email addresses into loginfo...
> 
> General question: Is it really expected that EVERYONE that wants to
> set up and use these contrib scripts have to read them, understand them
> and retro-engineer the inputs?

Apparently so.  It appears that you're expected to customize the
log_accum script for your environment.  In particular, look for the
mlist_map subroutine, both the definition of which and the call are
commented out.  It appears that you need to set $mlist to the list of
recipients somehow -- the commented out code provides one example but
you can do it any way you like.  The downside of that, of course, is
that you *have* to do it, whether you want to or not.

-Larry Jones

Hey!  What's the matter?  Can't you take a joke?!  It was a JOKE! -- Calvin


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs


RE: Format for 1.11.10's contrib's loginfo, used by log_accum com mit

2003-12-09 Thread Peter Connolly
> Perl isn't that hard to read.

Larry, Larry, Larry,...  Trust me. If you've never encountered constructs like @_, my, 
local($wd, @files); scalars, arrays... (and btw, 'local' is not local, 'my' is 
local...how cute), reading it is doable but tediously slow.  I'm reminded of a 
friend's admonition in college.  He said: "Physics is easy, once you know it."

> I believe you want something like:
> 
> commitinfo:
>   DEFAULT commit_prep -u ${USER}
> 
> loginfo:
>   DEFAULT log_accum -u ${USER} %s

I've tried that and when I commit, I get the following messages:

   Processing log script arguments...
   Mailing the commit message to (from [EMAIL PROTECTED])
   No recipient addresses found in header

which I guess means that $mail_to and its progenitor $addr_list in the 
 subroutine are not being set properlybut no hints as to how to 
format those email addresses into loginfo...

General question: Is it really expected that EVERYONE that wants to set up and use 
these contrib scripts have to read them, understand them and retro-engineer the inputs?


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs