<html><head><style type="text/css"></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div>I strongly disagree. Unless you want to write scripts to handle SCM(n). If the core Xorg libs/proto stuff moves to git, we might as well move all of the Xorg pieces to git. Modularization doesn't mean making buiding/developing on X even more difficult. I fully agree with Egbert. Either you pick one or you'll seriously impact X development.<br><br>Shawn.<br><br>----- Original Message ----<br>From: Diego Calleja <diegocalleja@gmail.com><br>To: xorg@lists.freedesktop.org<br>Sent: Tuesday, April 18, 2006 6:53:06 AM<br>Subject: Re: [SCM TRANSITION] Re: Proposal: move Randr protocol and library to git<br><br><div>El Tue, 18 Apr 2006 11:08:00 +0200,<br>Egbert Eich <eich@suse.de> escribió:<br><br>> - To take advantage of a new and improved API a user may have to<br>> upgrade numerous modules at once.<br><br>>From my own user perspective this doesn't matters that much. If you're<br>an user and you're trying new things you may need to download projects<br>not hosted in fdo.org, ej: kernel snapshots when dealing with drm or a<br>metacity version featuring some new feature. And from a user perspective<br>using several SCMs is not an issue at all, since you just do "cvs update",<br>"git pull", "svn whatever" or switch branches if anything. Also, for a <br>user the code is read-only, so it's possible to use git -> cvs gateways<br>if using several SCMs gets to be a problem.<br>_______________________________________________<br>xorg mailing list<br>xorg@lists.freedesktop.org<br><a target="_blank" href="http://lists.freedesktop.org/mailman/listinfo/xorg">http://lists.freedesktop.org/mailman/listinfo/xorg</a><br></div></div></div></div></body></html>