[pnfs] sorting out pnfs cvs

[William A. (Andy) Adamson]

On 2/26/07, J. Bruce Fields <bfields at fieldses.org> wrote:
>
> On Mon, Feb 26, 2007 at 04:33:18PM -0800, Iyer, Rahul wrote:
> > I'm a bit confused here as to what the plan is. Are we going to have a
> > git tree as well as a CVS tree? Or are we switching to git. In case it's
> > the latter, then is there a "red flag day" where we switch, and also,
> > when should I stop committing to the CVS tree?
>
> The plan is to switch completely, and it looks like we do
> (unfortunately) need a "red flag" day.  I guess I'll go ahead and make
> the cvs tree readonly tommorow if there's no objections.



first: i don't know how the  CVS tree wound up with non-pnfs changes being
commited. in the past, i have succesfully used 'cvs diff -r vendortag' on a
newly checked out tree to make a pnfs only patch. perhaps someone called cvs
commit on a tree that had more than pnfs changes.

anyway, we are in the position that it took a bit of work to get a pnfs only
patch from the CVS tree. so, i vote we move to GIT asap - make CVS read only
and stop committing. review bruces pnfs-only patch to make sure it is only
pnfs code, bring up the GIT tree with bruces pnfs-only patch, test it, and
then open the GIT tree to updates.

-->Andy

--b.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://linux-nfs.org/pipermail/pnfs/attachments/20070227/3d3fb15f/attachment-0001.htm