[cgl_discussion] Check in logs for recent CVS check-ins

Brugger, Andrea L andrea.l.brugger at intel.com
Fri Sep 6 09:55:32 PDT 2002

I admit I am guilty of doing this, but I believe I have a good reason.  This
particular check-in spans almost a month of work and is not a typical - "fix
one bug" - check-in, so it would have required re-entering the logs for all
of the check-ins for the past month otherwise.  I was hoping we could make
an exception here since we are syncing a lot of work rather than just
copying the cvs history, etc. as-is.

If there is a better way of retrieving the history than manually re-entering
the logs, please let me know so I can save some time (and do it right) for
the remainder of my sync-ups.


-----Original Message-----
From: Khalid Aziz [mailto:khalid at fc.hp.com]
Sent: Friday, September 06, 2002 9:47 AM
To: 'cgl_discussion at osdl.org'
Subject: [cgl_discussion] Check in logs for recent CVS check-ins

I have been looking at the recent check-ins into CVS and the log
messages for a number of those check-ins simply say "Changes since Aug
15", or "sync from TLT trek2 9/6/02". This breaks the rules set forth in
developer's guide on page 12 which says that when checking in code for a
bugfix , the log must refer to a bug number in bugzilla. If these
check-ins were not for bugfixes, they were rather functionality
enhancement, a more descriptive log would be extremely helpful.


Khalid Aziz                                   Linux Systems Division
(970)898-9214                                        Hewlett-Packard
khalid at fc.hp.com                                    Fort Collins, CO

"The Linux kernel is subject to relentless development" 
				- Alessandro Rubini
cgl_discussion mailing list
cgl_discussion at lists.osdl.org

More information about the cgl_discussion mailing list