Re: cvs diff on repository files
Maybe cou can invoke rcsdiff on the repository-files
themself, but - since cvs is only following rcs-syntax
- there might be warnings about some keys in the files
--- [EMAIL PROTECTED] schrieb: > Hello,
>
> I'm wanting to set up CVS to automatically mail a
> cvs diff whenever a
> file is committed. The problem is cvs diff doesn't
> seem to work from the
> repository, I get the following error:
>
> cvs diff: Cannot open CVS/Entries for reading: No
> such file or directory
>
> I set up CVSROOT/loginfo with the following line:
>
> DEFAULT $CVSROOT/CVSROOT/cvsdiff.pl %{sVv} >>
> ~/cvsdiff.log
>
> The cvsdiff.pl script does a cvs diff between the
> two revisions of each
> file and emails it to a mailing list for code
> review. But the cvs diff
> inside the script fails. Is there a solution that
> doesn't involve
> checking the directory out on the repository server,
> doing the diff, and
> removing the directory? I noticed that the log.pl
> in the contrib
> directory does a cvs status, which also fails for me
> with a similar
> message if run on repository files.
>
> Thanks,
> Aaron
>
>
>
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs
__
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Weihnachts-Einkäufe ohne Stress! http://shopping.yahoo.de
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs diff on repository files
[EMAIL PROTECTED] writes: > > The cvsdiff.pl script does a cvs diff between the two revisions of each > file and emails it to a mailing list for code review. But the cvs diff > inside the script fails. Is there a solution that doesn't involve > checking the directory out on the repository server, doing the diff, and > removing the directory? I noticed that the log.pl in the contrib > directory does a cvs status, which also fails for me with a similar > message if run on repository files. Look very carefully at how the log.pl script works -- it runs the command in the *current directory*, not the repository. The current directory is always a valid working directory (the user's working directory in local mode, a server-side copy in client/server mode). It also uses the global -n flag to allow the command to work despite the existing lock on the file. -Larry Jones I obey the letter of the law, if not the spirit. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
cvs diff on repository files
Hello,
I'm wanting to set up CVS to automatically mail a cvs diff whenever a
file is committed. The problem is cvs diff doesn't seem to work from the
repository, I get the following error:
cvs diff: Cannot open CVS/Entries for reading: No such file or directory
I set up CVSROOT/loginfo with the following line:
DEFAULT $CVSROOT/CVSROOT/cvsdiff.pl %{sVv} >> ~/cvsdiff.log
The cvsdiff.pl script does a cvs diff between the two revisions of each
file and emails it to a mailing list for code review. But the cvs diff
inside the script fails. Is there a solution that doesn't involve
checking the directory out on the repository server, doing the diff, and
removing the directory? I noticed that the log.pl in the contrib
directory does a cvs status, which also fails for me with a similar
message if run on repository files.
Thanks,
Aaron
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs diff on repository
On Sat, 2002-10-12 at 03:47, Larry Jones wrote: > [EMAIL PROTECTED] writes: > > > > cvs rdiff: [10:00:50] waiting for automan's lock in > > /home/cvs_automation/CVSROOT > > > > It will loop there until I Ctrl-C it. Apparently rdiff doesn't like to > > be run from within loginfo. Any way around it? > > Use the -n global option to ignore the locks. Alternatively, background the cvs rdiff command in the script. The commit is waiting for the cvs rdiff to finish (because it's called in a *info script), but the rdiff is waiting on the commit's lock. If you background the rdiff, the commit won't be waiting for it anymore. Jenn V. -- "Do you ever wonder if there's a whole section of geek culture you miss out on by being a geek?" - Dancer. [EMAIL PROTECTED] http://anthill.echidna.id.au/~jenn/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs diff on repository
[EMAIL PROTECTED] writes: > > cvs rdiff: [10:00:50] waiting for automan's lock in > /home/cvs_automation/CVSROOT > > It will loop there until I Ctrl-C it. Apparently rdiff doesn't like to > be run from within loginfo. Any way around it? Use the -n global option to ignore the locks. -Larry Jones It's either spectacular, unbelievable success, or crushing, hopeless defeat! There is no middle ground! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: cvs diff on repository
Thanks for the help. When I converted to using rdiff I get the following
error whenever I commit anything:
cvs rdiff: [10:00:50] waiting for automan's lock in
/home/cvs_automation/CVSROOT
It will loop there until I Ctrl-C it. Apparently rdiff doesn't like to
be run from within loginfo. Any way around it?
Thanks,
Aaron
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, October 10, 2002 5:32 PM
> > To: [EMAIL PROTECTED]
> > Subject: cvs diff on repository
> >
> > I'm wanting to set CVS up so that every time a file is
> > committed it will
> > send an email with the diffs to the other developers for code review.
> >
> > I added a line to the loginfo file:
> >
> > DEFAULT $CVSROOT/CVSROOT/cvsdiff.pl %{sVv}
> >
> > cvsdiff.pl is a script that does a cvs diff of the two versions and
> > emails the results. However, a cvs diff does not work on the
> > repository
> > files (",v"), it complains about missing CVS/Entries. Is
> > there a way to
> > get the diff of two different versions of a file from the
> > repository? I
> > noticed that the contrib/log.pl script is meant to be run from
loginfo
> > and does a cvs status, which also fails for me from the repository.
> >
> > Thanks for any help. I emailed a similar question yesterday before I
> > subscribed and got a reply saying that it's waiting for moderator
> > approval, so apologies if I end up posting this twice..
> >
> > Aaron
>
> cvs diff requires you to be in a work area.
> cvs rdiff allows you to do a diff without having a work area.
> Note that the rdiff uses the "-c" format showing a context diff of
three
> lines before and after the changes.
> Note that the status command does not have a corresponding rstatus
command
> because the status is comparing a work area to the repository. So your
> cvsdiff.pl program should not include a status command.
>
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
RE: cvs diff on repository
Hi Aaron,
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> [EMAIL PROTECTED]
>
> I'm wanting to set CVS up so that every time a file is committed it will
> send an email with the diffs to the other developers for code review.
>
> I added a line to the loginfo file:
>
> DEFAULT $CVSROOT/CVSROOT/cvsdiff.pl %{sVv}
>
> cvsdiff.pl is a script that does a cvs diff of the two versions and
> emails the results. However, a cvs diff does not work on the repository
> files (",v"), it complains about missing CVS/Entries. Is there a way to
> get the diff of two different versions of a file from the repository? I
> noticed that the contrib/log.pl script is meant to be run from loginfo
> and does a cvs status, which also fails for me from the repository.
I suppose cvs rdiff would solve your problem. It's described in the manual.
HTH
Martin
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
RE: cvs diff on repository
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 10, 2002 5:32 PM
> To: [EMAIL PROTECTED]
> Subject: cvs diff on repository
>
> I'm wanting to set CVS up so that every time a file is
> committed it will
> send an email with the diffs to the other developers for code review.
>
> I added a line to the loginfo file:
>
> DEFAULT $CVSROOT/CVSROOT/cvsdiff.pl %{sVv}
>
> cvsdiff.pl is a script that does a cvs diff of the two versions and
> emails the results. However, a cvs diff does not work on the
> repository
> files (",v"), it complains about missing CVS/Entries. Is
> there a way to
> get the diff of two different versions of a file from the
> repository? I
> noticed that the contrib/log.pl script is meant to be run from loginfo
> and does a cvs status, which also fails for me from the repository.
>
> Thanks for any help. I emailed a similar question yesterday before I
> subscribed and got a reply saying that it's waiting for moderator
> approval, so apologies if I end up posting this twice..
>
> Aaron
cvs diff requires you to be in a work area.
cvs rdiff allows you to do a diff without having a work area.
Note that the rdiff uses the "-c" format showing a context diff of three
lines before and after the changes.
Note that the status command does not have a corresponding rstatus command
because the status is comparing a work area to the repository. So your
cvsdiff.pl program should not include a status command.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
cvs diff on repository
I'm wanting to set CVS up so that every time a file is committed it will
send an email with the diffs to the other developers for code review.
I added a line to the loginfo file:
DEFAULT $CVSROOT/CVSROOT/cvsdiff.pl %{sVv}
cvsdiff.pl is a script that does a cvs diff of the two versions and
emails the results. However, a cvs diff does not work on the repository
files (",v"), it complains about missing CVS/Entries. Is there a way to
get the diff of two different versions of a file from the repository? I
noticed that the contrib/log.pl script is meant to be run from loginfo
and does a cvs status, which also fails for me from the repository.
Thanks for any help. I emailed a similar question yesterday before I
subscribed and got a reply saying that it's waiting for moderator
approval, so apologies if I end up posting this twice..
Aaron
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
