info-cvs
[Top][All Lists]
Advanced

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

Re: Asunto: Re: Asunto: Re: RV: CVS Notifications


From: Mark D. Baushke
Subject: Re: Asunto: Re: Asunto: Re: RV: CVS Notifications
Date: Tue, 13 Sep 2005 04:53:46 -0700

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

address@hidden writes:

> Now It works! thanks Mark.

Good.

> But is not doing what I suppose,I explain, my directory structure in cvs
> is
>  usr/crc/require/
>            |
>            +cas/
>            |
>            +pair/
>            |
>            +common/
> And what I expect is if the users make a commit like:
> (pwd = usr/crc/require/)
> cvs commit -m "TEST" file1  cas/file1 cas/file2 common/file1 pair/file1
> 
> That the commitlog get all the information os those files.
> It should work ?,I did not manage to.
> I see you are really expert on this area, do yo have any idea?

Each directory during the commit will be looked up in turn.

For your commit example,

The first tirgger will be run on a directory where usr/crc/file1 is passed

  %p == usr/crc
  %s == 'file1'

(echo;echo usr/crc; echo 'file1' 1.1 1.2; cat) >> $CVSROOT/CVSROOT/commitlog

The next trigger will be run on a directory where usr/crc/cas/file1 and
usr/crc/cas/file2 are passed as

  %p == usr/crc/cas
  %s == 'file1' 'file2'

(echo;echo usr/crc/cas; echo 'file1' 1.1 1.2 'file2' 1.4 1.5; cat) >> 
$CVSROOT/CVSROOT/commitlog

(assuming as a given, that file1 was originally version 1.1 and 1.2 was
committed and given that file2 was originally version 1.4 and 1.5 was
committed). The stdout passed via the cat command will contain the
standard text template passed to the loginfo trigger for your commit.

The next directory to be triggered would be the usr/crc/common directory
with 'file1' version.old version.new.

(echo;echo usr/crc/common; echo 'file1' 1.1 1.2; cat) >> 
$CVSROOT/CVSROOT/commitlog

The next directory to be triggered would be the usr/crc/pair directory
with the 'file1' version.old version.new arguments.

(echo;echo usr/crc/pair; echo 'file1' 1.1 1.2; cat) >> 
$CVSROOT/CVSROOT/commitlog

You may find that using the command:

cvs -t -t -t commit -m "TEST" file1 cas/file1 cas/file2 common/file1 pair/file1

will generate more information to help you understand what is happening.

        Good luck,
        -- Mark

> 
> Thanks in advance!!
> Jeroni
> 
> 
> >-- Mensaje original --
> >To: address@hidden
> >cc: "Satya Prasad D.V" <address@hidden>, address@hidden
> >Subject: Re: Asunto: Re: RV: CVS Notifications 
> From: "Mark D. Baushke" <address@hidden>
> >Date: Tue, 13 Sep 2005 02:53:01 -0700
> >
> >
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >address@hidden writes:
> >
> >> I thought the same but when I put the directory name It does not work
> either.
> >> The strange thing is that I can commit without error, but the commitlog
> >> do not change.
> >> In anyway thanks for your answer.
> >> Best Regards,
> >> Jeroni
> >
> >In the tree you care about, use the command:
> >
> >    cat CVS/Repository
> >
> >to see what is in that file. That is likely the value you want to use in
> >your loginfo file. You do NOT want trailing / characters.
> >
> >^usr/crc  (echo;echo %p; echo %{sVv}; cat) >> $CVSROOT/CVSROOT/commitlog
> >
> >should work fine. Note that the first match is the one that counts... it
> >will not help you to order the loginfo file such that substrings come
> >first and more explicit pathnames later.
> >
> >     Good luck,
> >     -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFDJr3KCg7APGsDnFERAqsuAKC429llPDnIGDPqj4yXt5PZH2jRzgCgrGm1
Xzk+RYrwkvcXz3V9Og9znOI=
=dwiS
-----END PGP SIGNATURE-----




reply via email to

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