On svn, it's not integrated yet. Roughly: curl http://...patchset.diff | patch -p0 # need to fix that: echo change id > ./.svn/gcl_info/temp_change gcl try temp_change gcl commit temp_change
The issue with that at the moment is that a @chromium.org user cannot use /close POST url (used by gcl on gcl commit) to close an issue he doesn't own, he must use the web interface. Once it's fixed, it will be much easier. If you feel compelled enough, send a patch to jam@ from somewhere in there: http://code.google.com/p/rietveld/source/browse/#svn/branches/chromium M-A 2009/5/3 Peter Kasting <[email protected]> > 2009/5/3 Evan Martin <[email protected]> > >> On Sun, May 3, 2009 at 10:57 AM, Paweł Hajdan Jr. >> <[email protected]> wrote: >> > How should I check whether someone has filed the CLA if it's his first >> patch >> > going to be committed? >> >> I don't know if there's a way to verify. I just ask if they're not in >> the AUTHORS file and put them in with their first commit after they've >> said they've filled it out. >> > > Yes, we can (and should) verify this. There's an internal file that keeps > these on record, I'm sure someone has the link and can check for you (last > time I had to do it I asked Pam). > > BTW, in case the original point of my message got obscured by Evan's git > comments, I reiterate: make sure to update the bug database after checking > in. > > PK > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
