RESOLVED FIXED 31967
update-webkit --chromium forces gclient sync 
https://bugs.webkit.org/show_bug.cgi?id=31967
Summary update-webkit --chromium forces gclient sync
Yaar Schnitman
Reported 2009-11-29 17:15:14 PST
gclient sync should be invoked with --force flag.
Attachments
update-webkit --chromium forces gclient sync (956 bytes, patch)
2009-11-29 17:17 PST, Yaar Schnitman 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Yaar Schnitman
Comment 1 2009-11-29 17:17:37 PST
Created attachment 43998 [details] update-webkit --chromium forces gclient sync
Darin Fisher (:fishd, Google)
Comment 2 2009-11-29 19:23:04 PST
Why is this necessary? Isn't it a bit unfriendly to developers that want to run update-webkit manually? Is this a mode that you want for the buildbots? If so is there an environment variable we can use to toggle this mode?
Yaar Schnitman
Comment 3 2009-11-30 08:59:15 PST
(In reply to comment #2) > Why is this necessary? Isn't it a bit unfriendly to developers that want to > run update-webkit manually? Is this a mode that you want for the buildbots? > If so is there an environment variable we can use to toggle this mode? Yes, this is unfriendly, but necessary for the bots. I will fix the unpleasantness in a subsequent patch.
Dimitri Glazkov (Google)
Comment 4 2009-11-30 09:02:41 PST
Comment on attachment 43998 [details] update-webkit --chromium forces gclient sync ok. Don't forget to file a follow-up bug to fix this.
WebKit Commit Bot
Comment 5 2009-11-30 09:10:44 PST
Comment on attachment 43998 [details] update-webkit --chromium forces gclient sync Clearing flags on attachment: 43998 Committed r51494: <http://trac.webkit.org/changeset/51494>
WebKit Commit Bot
Comment 6 2009-11-30 09:10:49 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.