From owner-cvs-usrbin Wed May 13 17:41:54 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27465 for cvs-usrbin-outgoing; Wed, 13 May 1998 17:41:54 -0700 (PDT) (envelope-from owner-cvs-usrbin) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27356; Wed, 13 May 1998 17:41:11 -0700 (PDT) (envelope-from julian@FreeBSD.org) From: Julian Elischer Received: (from julian@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id RAA04329; Wed, 13 May 1998 17:37:31 -0700 (PDT) Date: Wed, 13 May 1998 17:37:31 -0700 (PDT) Message-Id: <199805140037.RAA04329@freefall.freebsd.org> To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-usrbin@FreeBSD.ORG Subject: cvs commit: src/usr.bin/shar shar.sh Sender: owner-cvs-usrbin@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk julian 1998/05/13 17:37:31 PDT Modified files: (Branch: RELENG_2_2) usr.bin/shar shar.sh Log: Tree repair: This file was not on the RELENG_2_2 branch because RELENG_2_2 was a REVISION tag and not a branch tag. This happenned at 1.3 consequently, 2.2.5 and 2.2.6 were both released with shar.sh stuck at 1.3 from the mainline. 1.3 was the HEAD so that was ok I guess. I've made a RELENG_2_2 branch again and done a merge from current on it, so nothing should change, except that cvs update -rRELENG_2_2 -D"May 1" should now produce the right result again. This was teh only thing stopping cvs update -rRELENG_2_2 -D"May 1" from checking out a whole historical freebsd 2.2.x tree as of some specific date. Revision Changes Path 1.1.1.1.8.1 +11 -3 src/usr.bin/shar/shar.sh