From owner-freebsd-doc@FreeBSD.ORG  Sun Feb  1 14:42:04 2004
Return-Path: <owner-freebsd-doc@FreeBSD.ORG>
Delivered-To: freebsd-doc@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 61E1516A4CE; Sun,  1 Feb 2004 14:42:04 -0800 (PST)
Received: from aker.isnic.is (aker.isnic.is [193.4.58.91])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 6A50643D1D; Sun,  1 Feb 2004 14:42:03 -0800 (PST)
	(envelope-from root@aker.isnic.is)
Received: by aker.isnic.is (Postfix, from userid 0)
	id E49C18D11A; Sun,  1 Feb 2004 22:42:01 +0000 (GMT)
To: FreeBSD-gnats-submit@freebsd.org
From: Olafur Osvaldsson <oli@isnic.is>
X-send-pr-version: 3.113
X-GNATS-Notify: 
Message-Id: <20040201224201.E49C18D11A@aker.isnic.is>
Date: Sun,  1 Feb 2004 22:42:01 +0000 (GMT)
cc: docs@FreeBSD.org
Subject: The 'standard-supfile' should track its own branch
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Olafur Osvaldsson <oli@isnic.is>
List-Id: Documentation project <freebsd-doc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
	<mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc>
List-Post: <mailto:freebsd-doc@freebsd.org>
List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
	<mailto:freebsd-doc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Feb 2004 22:42:04 -0000


>Submitter-Id:	current-users
>Originator:	Olafur Osvaldsson
>Organization:	Internet a Islandi hf.
>Confidential:	no 
>Synopsis:	The 'standard-supfile' should track its own branch
>Severity:	non-critical
>Priority:	medium
>Category:	misc
>Class:		change-request
>Release:	FreeBSD 5.2-RELEASE i386
>Environment:

	
>Description:
	
The 'share/examples/cvsup/standard-supfile' should track its own branch.

Some time ago I was told that the standard-supfile should always have the branch tag
for the branch that it came from, this has not been the case with the RELENG_5_1,
RELENG_5_2 or the relevant RELENG_5_*_0_RELEASE branches.
>How-To-Repeat:
	
>Fix:
RELENG_5_1:
====================================================================================
--- share/examples/cvsup/standard-supfile.orig     Sun Feb  1 22:14:02 2004
+++ share/examples/cvsup/standard-supfile  Sun Feb  1 21:51:35 2004
@@ -51,7 +51,7 @@
 *default host=CHANGE_THIS.FreeBSD.org
 *default base=/usr
 *default prefix=/usr
-*default release=cvs tag=.
+*default release=cvs tag=RELENG_5_1
 *default delete use-rel-suffix

 # If you seem to be limited by CPU rather than network or disk bandwidth, try

====================================================================================
RELENG_5_2:
====================================================================================
--- share/examples/cvsup/standard-supfile.orig     Sun Feb  1 22:14:02 2004
+++ share/examples/cvsup/standard-supfile  Sun Feb  1 22:15:33 2004
@@ -51,7 +51,7 @@
 *default host=CHANGE_THIS.FreeBSD.org
 *default base=/usr
 *default prefix=/usr
-*default release=cvs tag=.
+*default release=cvs tag=RELENG_5_2
 *default delete use-rel-suffix

 # If you seem to be limited by CPU rather than network or disk bandwidth, try
====================================================================================

The same fix would be needed for RELENG_5_*_0_RELEASE if you want to fix that
and I'll send you the patches if needed.