This should still work fine. One person can lock the whole directory, then people who need to commit unforkage can lock the specific files they need to unfork using --force. That said, the only forkage that happens these days is when doing a webkit merge. What should the merger do if they find themselves needing to change files in third_party/WebKit (e.g. files in the platform/chromium directories)?
Ojan On Fri, May 1, 2009 at 8:46 AM, Dimitri Glazkov <[email protected]>wrote: > > Not yet. There's a small bunch of people still landing unforkages. > > :DG< > > On Fri, May 1, 2009 at 8:40 AM, Marc-Antoine Ruel <[email protected]> > wrote: > > svn lock? > > > > On Fri, May 1, 2009 at 11:35 AM, Dimitri Glazkov <[email protected]> > wrote: > >> > >> We are very, very close to total unforking. In order to facilitate the > >> completion of this process, please refrain from landing any changes in > >> trunk/deps/third_party/WebKit. This holds true even if your patch is > >> already approved upstream. So, to put it simply: > >> > >> NO MOAR THIRD_PARTY/WEBKIT COMMEETS. > >> > >> :DG< > >> > >> >> > >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
