Multi user

[Murali Potla]

Hi All,

How to set up a repository so that only some users will have permissions
to write and some other read access. What should be the permissions of
the directory.

Where i can i find a good document regarding cvs permissions

Thanks 
Murali


---SOFTPRO DISCLAIMER--

Information contained in this E-MAIL and any attachments are
confidential being  proprietary to SOFTPRO SYSTEMS  is 'privileged'
and 'confidential'.

If you are not an intended or authorised recipient of this E-MAIL or
have received it in error, You are notified that any use, copyiny or
dissemination  of the information contained in this E-MAIL in any
manner whatsoever is strictly prohibited. Please delete it immediately
and notify the sender by E-MAIL.

In such a case reading, reproducing, printing or further dissemination
of this E-MAIL is strictly prohibited and may be unlawful.

SOFTPRO SYSYTEMS does not REPRESENT or WARRANT that an attachment
hereto is free from computer viruses or other defects. 

The opinions expressed in this E-MAIL and any ATTACHEMENTS may be
those of the author and are not necessarily those of SOFTPRO SYSTEMS.



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

Re: Multi user

[Mahantesh M Vantmuri]

Murali Potla wrote:

How to set up a repository so that only some users will have permissions
to write and some other read access. What should be the permissions of
the directory.
Where i can i find a good document regarding cvs permissions
You can make use of standard unix permissions on modules. Check the 
latest cvs version, I think it has better access control options.
Also read CVS manual for how readers and writers groups work in CVS.

Cheers.
Mahanetsh.


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

Re: Unable to lock files

[Riechers, Matthew W]

"Amit Sharma (SCM)" wrote:
> 
> Hi All,
>I am not able to lock file from cvs. I have tried on both cvs1.2 and
> cvs1.3 individually. Now I have both version installed on my system. Every
> time I try to lock a file it gives following message-
> cvs [admin aborted]: 'admin -l' is a depreciated option.  Use 'edit -c'
> instead.
> 
> CVSServer Version is 1.11.5

I was able to reproduce this with the WinCVS client. The CVS that comes
with WinCVS prints this with 'cvs -v':

Concurrent Versions System (CVS) NT 1.11.1.1 (Local Build 27)
 (client/server)

You may want to contact the CvsGui project
. I'm not sure upgrading the
client will help, but they may have run into this problem before.

BTW, I didn't know options "depreciated" :)

-Matt


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

Re: Database file checkin - Summary

[Daniel Hurtubise]

Hi all,

After reading many replies I have concluded that the best thing to do, in my
humble opinion, is to create a .sql script that can build the database
schema from scratch as well as create all the stored procedures. Then I can
take this script and check it into CVS.

Next, any modifications to stored procedures and table definitions (ie.
Modify stored procedure or modify table) will be saved as sql statements and
stored in CVS (possibly as a patch). At the same time, the "master" creation
script will be modified and committed to CVS.

This will permit me to keep my DB architecture in sync with my web
application for new installs and it will also permit me to keep my existing
sites up to date.

This way, I'm keeping only text format in CVS and I have full control over
the database structure. Technically, if I had to, I could backup a database,
rebuild it from scratch using the master creation script and then restore
the database.

Regards,
Daniel.
On 3/10/03 23:46, "Gurpreet Singh (SCM)" <[EMAIL PROTECTED]> wrote:

> Hi 
> 
> well, for SQL server - the way (safe) is to be besides the normal way (.BAK
> / .DAT) of the DB itself is to export the SP's or other Data objects of a DB
> as a simple sql / txt format -  The best method to then checkin to a CVS
> repository. 
> 
> Regards
> Gurpreet S
> 
> -Original Message-
> From: Daniel Hurtubise [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 10, 2003 11:38 PM
> To: Sherzod Ruzmetov; 'CVS-II Discussion Mailing List'
> Subject: Re: Database file checkin
> 
> 
> Hi. The replies I received to date have been very helpful, thanks.
> I have a follow up question.
> 
> What do people typically do with stored procedures?
> 
> Or rephrased, do you save the stored procedures to a file and then check it
> into CVS, or do you simply do a backup as I described in my previous email?
> 
> Basically, I'm hunting for best practice, having no previous experience in
> this area.
> 
> Thanks in advance for your valued wisdom.
> 
> Daniel.
> On 3/10/03 11:21, "Sherzod Ruzmetov" <[EMAIL PROTECTED]> wrote:
> 
>>   : Has anybody checked in a database backup into CVS? I know
>>   : this may sound
>>   : odd, but I was thinking of taking a snapshot of my SQL
>>   : Server database in a
>>   : empty data state and then checking it into CVS.
>> 
>> 
>> I do a similar thing, but I keep ONLY table schemas, since I never
>> felt need to Version-Control the whole database. But if you
>> have a reason for doing so, and if you think CVS can help you
>> with it, give it a shot, and let the list know.
>> 
>>   : Will there be any issues with checking that backup out of
>>   : CVS and restoring
>>   : a new database from it?
>> 
>> No, there will not be, as long as your database backup is a text/plain
>> file (similar to the output of "mysqldump" utility), which makes more
>> sense.
>> 
>> sherzod
>> 
>> 
> 
> 
> 
> ___
> 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: Multi user

[Larry Jones]

Murali Potla writes:
> 
> How to set up a repository so that only some users will have permissions
> to write and some other read access. What should be the permissions of
> the directory.

It's somewhat terse, but everything you need to know is in the manual:



-Larry Jones

I think football is a sport the way ducks think hunting is a sport. -- Calvin


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

gui interface

[Derkaoui]

does someone knows about a user friendly interface for cvs on unix platform ?
thanksM. Derkaouiwho can do, do.  Who can't do, teach.  Who can't teach, critics.Lèche-vitrine ou lèche-écran ? Yahoo! Magasinage.___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

XML Schema and DTD for CVS Info in XML files?

[Herr Christian Wolfgang Hujer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello dear CVS users,


I'd like to know wether there already exists an XML Schema and a DTD to 
include CVS information in XML files.

Currently, we use the following approach to use CVS information in XML files:






This is not very convenient when the information shall be extracted during a 
transformation with XSLT / XPath.

I'd rather like to use:
http://www";
cvs:Id = "$Id$"
cvs:Source = "$Source"
-- ... --
>


It's much easier to extract information from attributes rather than from 
comments.

Are there already some "official" CVS Schema Modules and DTD modules which can 
easily be combined for instance with modularized XHTML (there I currently use 
meta elements) or modularized SVG to validate documents containing such CVS 
attributes?

If not, I'd develop some and provide them to the public (e.g. for inclusion 
with the CVS distribution).


Bye
- --
ITCQIS GmbH
Christian Wolfgang Hujer
Geschäftsführender Gesellschafter
Telefon: +49  (0)89  27 37 04 37
Telefax: +49  (0)89  27 37 04 39
E-Mail: [EMAIL PROTECTED]
WWW: http://www.itcqis.com/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+blaAzu6h7O/MKZkRAgktAJ9P6uN1n1s0nKoOzgyH3DkL+jvQGwCgtoHu
ZlXnpsBqSAMSCQ1UDGeDd+4=
=nG4/
-END PGP SIGNATURE-



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

loginfo log messages

[Grisinger, Daniel (MAN-Golden)]

Hiya!

I'm trying to capture the log message included with each commit, using a
filter specified in the loginfo file.  I don't seem to be getting the log
message, though.  I'm using this code:

  my $log_msg;
  my $infh = IO::File -> new('< -');  # open a filehandle to STDIN
  for ($infh -> getlines) {
$log_msg .= $_;
  }

which is modestly adapted from the contents of /usr/share/cvs/contrib/log on
a redhat 8.0 
system.  The $log_msg variable never gets populated with anything, though.

Am I doing something wrong?  CVS server version 1.11.1p1 and client version
1.11.2.

Thanks.

daniel






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

Re: loginfo log messages

[Larry Jones]

"Grisinger, Daniel (MAN-Golden)" writes:
> 
>   my $log_msg;
>   my $infh = IO::File -> new('< -');  # open a filehandle to STDIN
>   for ($infh -> getlines) {
> $log_msg .= $_;
>   }

I think you've confused info-cvs with a perl list.

-Larry Jones

I won't eat any cereal that doesn't turn the milk purple. -- Calvin


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

Java/CVS question

[Eric C. Hein]

I'm using the java Runtime class to update files 
from a CVS repository and in some cases it is hanging (see comment in 
code).  I think this may have something to do with the buffer size for 
the standard input and output streams of the OS (Win2k).   If I close 
my java app the files do update correctly. Any ideas on how to resolve 
this? 
 
Thanks
 
 
public String execute(String[] args) {
 
  StringBuffer result = new 
StringBuffer();  String str;  Process 
m;
 
  try {
 
   String [] cmd = 
{"cmd.exe","/c",args[0]};   m = 
Runtime.getRuntime().exec(cmd);
 
   BufferedReader in 
=new BufferedReader(new 
InputStreamReader(   
m.getInputStream()));
 
   while((str = in.readLine()) != 
null) 
{System.out.println(str);result.append("\n" 
+ str);   }
 
// *** code hangs before it gets here 
**
 
   m.waitFor();   System.out.println("Process 
exit code is:" + m.exitValue());   
  }  catch(Exception ex) 
{   ex.printStackTrace 
();  }  return 
result.toString(); }
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: loginfo log messages

[Grisinger, Daniel (MAN-Golden)]

Larry Jones <[EMAIL PROTECTED]> writes:

> "Grisinger, Daniel (MAN-Golden)" writes:
> > 
> >   my $log_msg;
> >   my $infh = IO::File -> new('< -');  # open a filehandle to STDIN
> >   for ($infh -> getlines) {
> > $log_msg .= $_;
> >   }
> 
> I think you've confused info-cvs with a perl list.

Well, no, I haven't.  The perl is correct, it simply reads from STDIN. The
problem is unquestionably a cvs issue.  But since that's the attitude here's
the
shell code that also doesn't work.


  #!/bin/bash
  #
  #  test cvs loginfo system

  cat < /dev/stdin >> /home/cvsuser/logtest


after running a commit there is no data added to logtest.

Here's the python code that also fails:


  #!/usr/bin/python

  import sys

  line=sys.stdin.read()

  while line:
  sys.stdout.write(line)
  line=sys.stdin.read()



when redirected to the logtest file nothing ever shows up.

if you'd like i can also send the c, c++, and java code that fail to find
anything on STDIN when invoked from loginfo, or you can just tell me whether
or not i'm doing something wrong.

sheesh.

daniel


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

Pruning empty directories from the cvsweb display

[Myhre, Julie]

Title: Pruning empty directories from the cvsweb display






My group uses CVSWeb  on a Linux box for viewing the status and contents of the cvs repository….much easier to get a handle on it than using ls. All our checking out,etc. is done an the command line.

I understand that if you delete all the files from a directory and use the -p option on the update, that will delete the directory from your working directory set.  But in the CVSWeb repository view, is there any way to indicate that this directory has been deleted?    I guess it can't really go away because of maintaining history, so the web view wouldn't stop displaying the directory name - but can that name be flagged in some way to indicate that it is a directory that has been deleted?

Thanks,

Julie Myhre




This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.


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

Re: XML Schema and DTD for CVS Info in XML files?

[Deron Meranda]

> Currently, we use the following approach to use CVS information in XML files:
> ...
> 


Comments also don't work well because the "--" (hyphen-hyphen)
sequence is illegal in XML comments.  In fact, even with elements you
probably need to use CDATA escapes.  I would definitely place a $Log$
inside an element body, as in

   

Other tags could probably either be inside attributes or elements,
depending upon how structured the value is.

I do agree that XML namespaces should be used.

One big problem with automatically inserting text into a document is
that of character sets.  What if the XML document uses UTF-16 rather
than UTF-8 or even ISO-8859-15?  But I don't know if that is easily
solved.  Of course XML basically dictates that UTF-8 is the default
unless its either explicitly specified or it can be automatically
detected to be something else.

-- 
Deron Meranda


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

RE: loginfo log messages

[Grisinger, Daniel (MAN-Golden)]

Larry Jones <[EMAIL PROTECTED]> writes:

> "Grisinger, Daniel (MAN-Golden)" writes:
> > 
> > Larry Jones <[EMAIL PROTECTED]> writes:
> > > 
> > > I think you've confused info-cvs with a perl list.
> > 
> > Well, no, I haven't.  The perl is correct, it simply reads 
> from STDIN. The
> > problem is unquestionably a cvs issue.  But since that's 
> the attitude here's
> > the
> > shell code that also doesn't work.
> 
> Are you *sure* the perl is correct?

Yes.  Running it outside of CVS results in STDIN being echoed back out.

> Have you checked to see if your script is executing at all?

It is.  The script mails a summary of changes out to the other developers on
my team.  This summary is complete except for the logmsg field.  I'm getting
the rest of the params (repository directory, file changed, old rev, new
rev)
passed through in ARGV.  There just isn't anything on STDIN to read from
(which
is where I expected to find the data, based on the CVS manual).

> What is the exact content of your $CVSROOT/CVSROOT/loginfo file?

DEFAULT (/home/cvsuser/cvs-scripts/cvs-mail-checkin-notifications %{sVv} >>
/home/cvsuser/cvslogs/commit-mailer.log 2>&1)&

I've also tried:

DEFAULT (sleep 3; /home/cvsuser/cvs-scripts/cvs-mail-checkin-notifications
%{sVv} >> /home/cvsuser/cvslogs/commit-mailer.log 2>&1)&

I removed the call to sleep(1), because I thought that maybe it was
eating STDIN before my script could get at it.  The current script sleeps
for a bit to give CVS time to clear locks (since it calls cvs internally).

There are no other entries in the loginfo file besides the DEFAULT.  (If
my company's dumb windows mail client wrapped that line, be assured that
it actually appears as a single line in the loginfo file.)

> What is the exact command you used for the commit and what was the exact
output?

$ cvs commit -m 'test commit' scrubber.c
Checking in scrubber.c;
/home/cvsuser/repository/is_devel/src/scrubsys/scrubber.c,v <-- scrubber.c
new revision: 1.17; previous revision: 1.16
done
$

Nothing is coming on STDIN, which is what I expected.  I could always call
cvs log from within the script and parse the latest log message out of it,
but the manual suggests that I should be seeing the log message coming in
on my standard input. 

Thanks.

daniel


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

Re: loginfo log messages

[Larry Jones]

"Grisinger, Daniel (MAN-Golden)" writes:
> 
> Larry Jones <[EMAIL PROTECTED]> writes:
> > 
> > I think you've confused info-cvs with a perl list.
> 
> Well, no, I haven't.  The perl is correct, it simply reads from STDIN. The
> problem is unquestionably a cvs issue.  But since that's the attitude here's
> the
> shell code that also doesn't work.

Are you *sure* the perl is correct?  Have you checked to see if your
script is executing at all?  What is the exact content of your
$CVSROOT/CVSROOT/loginfo file?  What is the exact command you used for
the commit and what was the exact output?

-Larry Jones

There's a connection here, I just know it. -- Calvin


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

Re: XML Schema and DTD for CVS Info in XML files?

[Herr Christian Wolfgang Hujer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello Deron, dear list members,


Am Dienstag, 11. März 2003 23:48 schrieb Deron Meranda:
> > Currently, we use the following approach to use CVS information in XML
> > files: ...
> > 
>
> Comments also don't work well because the "--" (hyphen-hyphen)
> sequence is illegal in XML comments.  In fact, even with elements you
> probably need to use CDATA escapes.  I would definitely place a $Log$
> inside an element body, as in
>
>

That's a good idea but not always possible, for instance, when there's an easy 
approach to add attributes but adding elements is very difficult.
We simply forbid the "--" in CVS Logs, as we forbid < and & and TODO.
But that's a solution working fine on a small group, whereas a widespread 
solution must of course take into account that some won't be aware of the 
"--" problem (why should they care about "--", anyway).

Thank you for the hint.


> Other tags could probably either be inside attributes or elements,
> depending upon how structured the value is.
> I do agree that XML namespaces should be used.
Yeah, I like them :-)

> One big problem with automatically inserting text into a document is
> that of character sets.  What if the XML document uses UTF-16 rather
> than UTF-8 or even ISO-8859-15?  But I don't know if that is easily
> solved.  Of course XML basically dictates that UTF-8 is the default
> unless its either explicitly specified or it can be automatically
> detected to be something else.
Thank you very much for pointing this out.
I work in an ideal environment: A Linux system completely configured to use 
UTF-8 (yeah, I do not use GNOME for that reason).
All files - Java, Perl, PHP, XML, /etc/passwd etc. are encoded in UTF-8.

Currently, if the CVS log is included in an XML document, the log's author 
must always be aware of the restriction XML might imply on the log comment.

But this problem is generic to automatically inserting bytes into a file 
format like XML, it is not specific to the combination CVS / XML, so I do not 
think it is a problem I could solve - or do you have a hint? Actually I'd not 
try to solve that problem because I see no chance to do so.


I could imagine a CVS-XML-solution with a Schema defining the simple types 
(based on regular expressions) required for the CVS Keywords, a Schema to 
choose to use attributes only, a Schema to use elements only and a Schema to 
use both - and of course a corresponding set of modules for extending old 
DTD-based XHTML / SVG.

Are you (Deron and other list members) interested?


Bye
- -- 
ITCQIS GmbH
Christian Wolfgang Hujer
Geschäftsführender Gesellschafter
Telefon: +49  (0)89  27 37 04 37
Telefax: +49  (0)89  27 37 04 39
E-Mail: [EMAIL PROTECTED]
WWW: http://www.itcqis.com/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+bncQzu6h7O/MKZkRAiuOAKDPDUAaZm9oZLfjhcMK1jYqNVxaQQCfUcwx
AYVMvee+/rAshFF8Areb3Fg=
=xYaO
-END PGP SIGNATURE-



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

RE: loginfo log messages

[Mark]

--- "Grisinger, Daniel (MAN-Golden)" <[EMAIL PROTECTED]> wrote:
> Larry Jones <[EMAIL PROTECTED]> writes:

> > What is the exact content of your $CVSROOT/CVSROOT/loginfo file?
> 
> DEFAULT (/home/cvsuser/cvs-scripts/cvs-mail-checkin-notifications %{sVv} >>
> /home/cvsuser/cvslogs/commit-mailer.log 2>&1)&

> Nothing is coming on STDIN, which is what I expected.  I could always call
> cvs log from within the script and parse the latest log message out of it,
> but the manual suggests that I should be seeing the log message coming in
> on my standard input. 

For STDIN,

DEFAULT /home/cvsuser/cvs-scripts/cvs-mail-checkin-notifications %{sVv} >>
/home/cvsuser/cvslogs/commit-mailer.log

Or for everything in ARGV,

DEFAULT (echo ""; echo %{sVv}; cat) | xargs
/home/cvsuser/cvs-scripts/cvs-mail-checkin-notifications >>
/home/cvsuser/cvslogs/commit-mailer.log

Mark


__
Do you Yahoo!?
Yahoo! Web Hosting - establish your business online
http://webhosting.yahoo.com


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

Setting access to specific modules in a repository

[Ramachandran, Harish (Cognizant)]

Hi,

I am using CVS NT system. In that i have one repository by name "project" and under 
that i have different modules. I have set up "pserver" authentication for repository 
access. Can i set user access to my repository module wise??


Thanks,
Harish
This e-mail and any files transmitted with it are for the sole use of the intended 
recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and 
destroy all copies of the original message. 
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or 
copying of this email or any action taken in reliance on this e-mail is strictly 
prohibited and may be unlawful.

Visit us at http://www.cognizant.com
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Re: loginfo log messages

[Dan Peterson]

On Tue, 11 Mar 2003 [EMAIL PROTECTED] wrote:

> On Tue, 11 Mar 2003 [EMAIL PROTECTED] wrote:
>
>> What is the exact content of your $CVSROOT/CVSROOT/loginfo file?
>
> DEFAULT (/home/cvsuser/cvs-scripts/cvs-mail-checkin-notifications %{sVv} >> 
> /home/cvsuser/cvslogs/commit-mailer.log 2>&1)&

I believe the reason you're not seeing anything on STDIN is because you're
putting the process in the background.  The data the CVS server sends to
STDIN is going to the parent of the background process, not the background
process itself.

You can solve this in a few different ways:

1. Don't put the process in the background:

  DEFAULT myscript %{sVv} >> mylog 2>&1

If the script is quick or you don't care that the commit will wait until
the script is done, then you don't need to put it in the background.

One note of caution in this case, don't try to issue any CVS commands
within the script that act on the same module (eg. cvs rlog).  If you do,
you'll get a "waiting on lock" message, because the "commit" is waiting
until the loginfo script returns before unlocking the module.

2. Force the parent of your background process to send STDIN to the
background child process:

  DEFAULT cat | (myscript %{sVv} >> mylog 2>&1) &

3. Run the script in the foreground... just log enough to read in STDIN,
then have it put itself into the background:

  DEFAULT myscript %{sVv} >> mylog 2>&1

And the script might look something like:

  ---
  #!/usr/bin/perl

  # Read STDIN before going into the background.
  my $stdin = do { local $/;  };

  # Fork a child process and exit from the parent.
  fork() and exit(0);

  # Let the child process sleep for a bit if you want.
  sleep(2);

  # Do stuff that takes a long time.

  # Do something with the original stuff from STDIN.
  print($stdin);

  exit(0);
  ---

PS. I've seen some cases where the commit hung around until the background
process was complete and I'm not 100% sure why.  One thing I've done to
get around it is to fork, then in the child process, chdir('/'), close
STDIN, STDOUT and STDERR and POSIX::setsid().  This will make sure the
background process is completely disassociated with the parent - different
process group and parent is now init (eg. 1).

Of course if you close STDOUT, then you'll need to print to something
other than STDOUT or you'll need to dup STDOUT before closing it.

PPS. You should also be very cautious using the %{sVv} string if any of
your file/directory names contain spaces.


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

Re: loginfo log messages

[Gagneet Singh]

Hi!

What are you trying to do? Are you wanting to send the log message written
when commiting files to CVS, to the various developers concerned?

Well! Then won't it be simpler to use the following, in the loginfo file in
$CVSROOT/CVSROOT folder:

DEFAULT (id; echo %{sVv}; date; cat) | mail [EMAIL PROTECTED]

This is the format I use and it sends the log message and the version
history to the people concerned, as for me [EMAIL PROTECTED] is a
mailing list of a group of the developers for the particular proect.

Hope this helps

Gagneet




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