[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: cvs diff on repository
From: |
aaron . brice |
Subject: |
RE: cvs diff on repository |
Date: |
Fri, 11 Oct 2002 10:06:56 -0700 |
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: address@hidden [mailto:address@hidden
> > Sent: Thursday, October 10, 2002 5:32 PM
> > To: address@hidden
> > 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.
>