[lug] CVS logging question

[Holshouser, David]

P stands for patched. I'm not sure how this is different than Merged except
in how cvs does the join.
I think a merge brings down the whole file to merge whereas Patch brings
down the diff.

Can't you can ask cvs for this information with a specific view log command?

> -----Original Message-----
> From:	Nate Duehr [SMTP:nate at natetech.com]
> Sent:	Tuesday, March 27, 2001 11:17 AM
> To:	lug at lug.boulder.co.us
> Subject:	Re: [lug] CVS logging question
> 
> That sounds like a job for "watches".
> 
> On Tue, Mar 27, 2001 at 11:58:07AM -0700, Scott A. Herod wrote:
> > Hi Ken,
> > 
> > I basically want a global change log.  A couple of us, all located
> > in different places, are working on a project.  I typically do
> > a "cvs commit" every evening and "cvs update" every morning.
> > It would be nice to have one file where I could check to see
> > what has been logged as changed by the others.
> > 
> > (BTW, what does a "P" mean in the update output?  It's not 
> > mentioned in the man page.)
> > 
> > Scott
> > 
> > Ken Weinert wrote:
> > > 
> > > I'm a bit confused - can you explain the purpose a bit more? Because
> > > normally a file won't be checked back in if it hasn't changed.
> > > 
> > > And if it hasn't changed, what kind of things are you trying to get
> > > logged?
> > > 
> > > * Scott A. Herod (herod at interact-tv.com) [010327 17:32]:
> > > > A question for some CVS experts.
> > > >
> > > > Is there a way to automatically create a change log in CVS?
> > > > Basically, I want something that always records the log message
> > > > whenever any file is checked back in.  I know that there is a
> > > > $Log: $ variable but it is only updated on the files that
> > > > change.  I want something that acts as if it always needs to
> > > > be updated.
> > > 
> > > --
> > > Ken Weinert   kenw at ihs.com 303-858-6956 (V) 303-705-4258 (F)
> > > GnuPG KeyID: 9274F1CE           GnuPG available at
> http://www.gnupg.org/
> > > GnuPG Key Fingerprint: 1D87 3720 BB77 4489 A928  79D6 F8EC DD76 9274
> F1CE
> > > 3 kinds of people: those who can count & those who can't.
> > > 
> > >
> ------------------------------------------------------------------------
> > >    Part 1.2Type: application/pgp-signature
> > _______________________________________________
> > Web Page:  http://lug.boulder.co.us
> > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> 
> -- 
> Nate Duehr <nate at natetech.com>
> 
> GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
> Public Key available upon request, or at wwwkeys.pgp.net and others.
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug