From owner-freebsd-hackers  Wed Jun 25 02:26:03 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id CAA12969
          for hackers-outgoing; Wed, 25 Jun 1997 02:26:03 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA12964
          for <hackers@freebsd.org>; Wed, 25 Jun 1997 02:25:59 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id TAA28921; Wed, 25 Jun 1997 19:23:53 +1000
Date: Wed, 25 Jun 1997 19:23:53 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199706250923.TAA28921@godzilla.zeta.org.au>
To: hackers@freebsd.org, j@uriah.heep.sax.de
Subject: Re: libedit, etc. (CVS issues)
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> Final question; should I add $Id$ strings to these files as they're
>> changed?
>
>Yes.  They will probably be converted into $FreeBSD$ some day, but
>they should be there to track possible own modifications.  The
>$NetBSD$'s are useful to see which version it came from (so once the
>NetBSD people opened their CVS, you could make cvs diffs ;-).

No.  The $NetBSD$'s are enough for the new changes.  There should be
$Id$'s for some of the old changes.  There shouldn't be $Id$ for the old
changes that are just patches from Lite2 (Lite2 still hasn't been imported
in most places outside of sys).  Don't do new commits just to fix $Id$'s.
We already have > 30000 useless log messages about changing $Id$'s.

Bruce