[GRASS5] Jan's copyright notice ++
Eric Mitchell
emitchell at altaira.com
Mon Nov 13 10:57:27 EST 2000
In my experience, the $Log$ tags mostly get in the way
of any perusing of the source code. Unless someone
takes the time to trim them, you can quickly end up
with a log section longer than the actual source in the
module. As soon as someone trims the file, you lose
some of the history you might have wanted to retain.
Also, anytime you want to do a cvs diff between
revisions, you get a lot of diffs that aren't relevant
to the source code mods.
It's possible to convince CVS to retain the history
associated with the files. CVS is, after all, just
serving RCS format files. By copying the ,v files
to the new repository, the new files will retain their
history, and a "cvs log" on them will give prior log
messages.
> > Without any experience with this problem, I would recommend that we do
> > not use the $Log$ keyword to avoid what could be major headaches in the
> > future given the size of Grass. Am I being paranoid? What do people
> > think?
--
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
| Eric B. Mitchell mailto:emitchell at altaira.com |
| tel: (301) 809 - 3534 Altair Aerospace Corporation |
| tel: (800) 7 - ALTAIR 4201 Northview Dr. Suite 410 |
| fax: (301) 805 - 8122 Bowie, MD 20716 |
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
,___
/"\ / o=\ /"""---===/
/ \_/ \__/ ---===/
| //\ || /""TT""/ //\ || ||""\
| // \ || || // \ || ||__/
| //--==\ |L--/ || //--==\ || || "=,
\ ---===/
\____---===/
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'
More information about the grass-dev
mailing list