The 'standard-supfile' should track its own branch

Olafur Osvaldsson oli at isnic.is
Sun Feb 1 22:42:04 UTC 2004


>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.

	




More information about the freebsd-doc mailing list