X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C810DD.98074A64@onstor-exch02.onstor.net>; Wed, 17 Oct 2007 08:48:50 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: Integrating changes from dev branch to other branches
Date: Wed, 17 Oct 2007 08:48:49 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E060D179A@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Integrating changes from dev branch to other branches
Thread-Index: AcgQ3Zc8CgOtKphNT5WvnnVM+siy+w==
From: "Brian DeForest" <brian.deforest@onstor.com>
To: "dl-Software" <dl-software@onstor.com>,
	"Ken Renshaw" <ken.renshaw@onstor.com>

Just a reminder that when you integrate changelists from the dev branch
into other (e.g. release) branches, please cut/paste the same comment
from the original (dev) changelist into the 2nd changelist in order to
preserve the file history and minimize the need to lookup additional
changelists (aka "Perforce archaeology"). =20

There have been a few recent integrations into the 3.1 release branch
where the comment simply references the original changelist, something
like:

	Integrate changelist XXXXX into 3.1 branch

It is preferable to cut/paste the original comment from changelist
XXXXX, such as:

	Integrate changelist XXXXX into 3.1 branch
	< changelist XXXXX comment goes here >

Thanks.
Brian
