Brian Paul wrote:
Keith Whitwell wrote:
Hmm - I think that's a side issue to this reorg. Let's keep to code that exists - I'm not sure that everyone's communicating acurately at the moment.
I think that there will probably always be some small details about the code that don't accurately map onto how the repository works, and also that talking about code is fairly error prone compared to actually working with it.
Brian - I'm happy to make a start with your original layout. Lets get that up and running so that we can talk in concrete terms about any additional & minor rearrangements for the final switchover.
Right.
So then, if anyone has anything they want to check into Mesa CVS do it soon and then be prepared to go a few days without check-ins. I don't want the repository changed while I'm working on a local copy.
I may begin work this evening (around 7pm mountain time). When I begin I'll post a "no more check-ins" message.
Just to double check we're on the same page - the new tree won't try and include the cvs history prior to this point, right? We're starting a new tree from scratch and leaving the history in the old one?
No, I want to preserve file histories wherever possible in the new tree.
I don't know about you, but I often look back through the CVS revisions to recall when/why things were changed. I use the SourceForge CVS browser/differencer a lot.
-Brian
------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
