<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><b>What is happening?</b></div><div><b><br></b></div><div>The Lustre source <span class="Apple-style-span" style="font-family: monospace; ">repository is moving from CVS, where it has lived for the last 7+ years to Git. This will simplify ongoing development of Lustre in a number of ways, including tracking of changes and history, improved merging of development branches into releases, and offline development.</span></div><span class="Apple-style-span" style="font-family: monospace; "><br>Unfortunately, due to the lengthy use and abuse of CVS to manage the Lustre code, it is not possible to do a straight import of the entire CVS repository into Git using any existing tools. Rather than simply importing the current state of the code into Git and lose all of the history, we've worked to import the major development branches along with their full history into a single Git repository to maximize its usefulness.</span><div><font class="Apple-style-span" face="monospace"><br></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="font-family: Monaco; "><div><b>When is this happening?</b></div><div><br></div><div>Monday December 14 2009 is the target date for switching all Lustre development from CVS to Git. <br><div><br></div><div>All CVS Repositories will transition to read-only state on Friday December 11, 2009 at 9:00 am CST. The CVS repository will remain in this read-only state for the duration of the conversion process. Please make your plans accordingly.</div><div><br></div><div>The conversion to Git will be done over the weekend (12/11/2009 - 12/13/2009). The resulting Git repository will be available on Monday December 14 2009 at 12:00 PM CST. The CVS tree will remain in a read-only state from this point on. All subsequent code changes must be done via Git.</div><div><br>Instructions on using Git with the Lustre code base can be found here: </div><div><font class="Apple-style-span" face="monospace"><font class="Apple-style-span" face="Monaco"><br></font></font></div><div><span class="Apple-style-span" style="font-family: monospace; "><a href="http://wiki.lustre.org/index.php/Accessing_Lustre_Code">http://wiki.lustre.org/index.php/Accessing_Lustre_Code</a><br><a href="http://wiki.lustre.org/index.php/Applying_Lustre_Patches_to_a_Kernel">http://wiki.lustre.org/index.php/Applying_Lustre_Patches_to_a_Kernel</a><br><a href="http://wiki.lustre.org/index.php/Submitting_Patches">http://wiki.lustre.org/index.php/Submitting_Patches</a></span></div><div><br><b>What is supported?</b></div><div><br></div><div>Following Branches are migrated to GIT</div><div><br><span class="Apple-tab-span" style="white-space: pre; "> </span>b1_6<br> <span class="Apple-tab-span" style="white-space: pre; "> </span>b1_8<br> <span class="Apple-tab-span" style="white-space: pre; "> </span>b_release_1_6_7<br> <span class="Apple-tab-span" style="white-space: pre; "> </span>b_release_1_8_0<br> <span class="Apple-tab-span" style="white-space: pre; "> </span>b_release_1_8_1</div><div> <span class="Apple-tab-span" style="white-space: pre; "> </span>master aka HEAD represents 2.0 work<br><br>A limited number of tags are also supported in the git repository. Only v* tags post 1.6.7 are supported. </div><div><br></div><div><b>What is not supported?</b><br><br></div><div><span class="Apple-tab-span" style="white-space: pre; "> </span>b1_4 branch will not be migrated and will be maintained under cvs.</div><div><br></div><div><b>Developer Migration Notes</b><br><br>To make your migration to git easier you should update any of your development CVS branches from the base, and land outstanding work in those development branches before Friday December 11, 2009. Working directories that contain uncommitted changes should also be updated, but can be done after the migration while the CVS repository is in a read-only mode.</div><div> </div><div>Tags will be placed in the CVS repository to mark the point were the conversion was done:</div><div><br></div><div> B1_6_GIT_BASE</div><div> B1_8_GIT_BASE</div><div><div> B_RELEASE_1_6_7_GIT_BASE</div><div> B_RELEASE_1_8_0_GIT_BASE</div><div> B_RELEASE_1_8_1_GIT_BASE</div><div> B2_0_GIT_BASE</div><div><br></div><div>In addition tags will also be in place in the Git repository marking the spot of the conversion:</div><div><br></div><div> GIT_EPOCH_B1_6</div><div> GIT_EPOCH_B1_8</div><div> GIT_EPOCH_B_RELEASE_1_6_7</div><div> GIT_EPOCH_B_RELEASE_1_8_0</div><div> GIT_EPOCH_B_RELEASE_1_8_1</div><div> GIT_EPOCH_MASTER</div></div><div><br></div><div><b>Support</b><br></div><div><b><br></b></div><div><a href="mailto:lustre-devel@sun.com">lustre-devel@sun.com</a></div></div></span></font></div></body></html>