|
|
Created:
7 years, 7 months ago by Isaac (away) Modified:
7 years, 7 months ago Reviewers:
szym, iannucci, Marc-Antoine Ruel (Google), M-A Ruel CC:
chromium-reviews, Dirk Pranke, cmp-cc_chromium.org, iannucci+depot_tools_chromium.org, abarth-chromium, eseidel Visibility:
Public. |
DescriptionAdd option to prevent gclient from changing remote
Allow users to set a git config entry which stops
gclient from messing with remote.origin.url. Useful
for using experimental repos.
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=199532
Patch Set 1 #
Total comments: 1
Created: 7 years, 7 months ago
Messages
Total messages: 12 (0 generated)
Why not use 'custom_deps': { 'src/third_party/WebKit': None } ?
A couple reasons: 1) Since refs/heads/* folders are the same, this makes gclient treat the experimental folder the same as if it were the official repo, doing the same syncing behavior as before. 2) This will also be used for https://chromium.googlesource.com/experimental/chromium/src/ WDYT?
On 2013/05/10 17:40:19, Isaac wrote: > A couple reasons: > > 1) Since refs/heads/* folders are the same, this makes gclient treat the > experimental folder the same as if it were the official repo, doing the same > syncing behavior as before. > > 2) This will also be used for > https://chromium.googlesource.com/experimental/chromium/src/ > > WDYT? I still think this is wrong and the setup is improperly done but lgtm.
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/ilevy@chromium.org/14731015/1
Message was sent while issue was closed.
Change committed as 199532
Message was sent while issue was closed.
Thanks M-A. I realize this workflow isn't normal. At some point we'll allow pushes to the official git repos in refs/wip, so this is a temporary solution that mimics the planned future workflow. I appreciate the review.
Message was sent while issue was closed.
On 2013/05/10 21:04:07, Isaac wrote: > Thanks M-A. I realize this workflow isn't normal. At some point we'll allow > pushes to the official git repos in refs/wip, so this is a temporary solution > that mimics the planned future workflow. > > I appreciate the review. For the record, if the name was more self-descriptive, like remote.gclient.autofix_url = False, I'd be much less concerned. In particular, gclient only touches origin so using remote.origin.gclient is not necessary.
oops, I meant remote.origin.client.auto_fix_url. Le 11 mai 2013 08:15, <maruel@chromium.org> a écrit : > On 2013/05/10 21:04:07, Isaac wrote: > >> Thanks M-A. I realize this workflow isn't normal. At some point we'll >> allow >> pushes to the official git repos in refs/wip, so this is a temporary >> solution >> that mimics the planned future workflow. >> > > I appreciate the review. >> > > For the record, if the name was more self-descriptive, like > remote.gclient.autofix_url = False, I'd be much less concerned. In > particular, > gclient only touches origin so using remote.origin.gclient is not > necessary. > > https://chromiumcodereview.**appspot.com/14731015/<https://chromiumcodereview... >
Message was sent while issue was closed.
https://chromiumcodereview.appspot.com/14731015/diff/1/gclient_scm.py File gclient_scm.py (right): https://chromiumcodereview.appspot.com/14731015/diff/1/gclient_scm.py#newcode322 gclient_scm.py:322: self._Capture(['config', 'remote.origin.gclient']) != 'getoffmylawn'): If the url is different and remote.origin.gclient is not set, gclient fails with: Error: Command git config remote.origin.gclient returned non-zero exit status 1 in XXXX/src/third_party/WebKit
Message was sent while issue was closed.
Thanks, yes it is currently broken. A fix is landing shortly in crrev.com/15325003. |