HomeSort by relevance Sort by last modified time
    Searched full:upload (Results 151 - 175 of 929) sorted by null

1 2 3 4 5 67 8 91011>>

  /external/chromium_org/chrome/common/extensions/docs/templates/articles/manifest/
key.html 21 <a href="https://chrome.google.com/webstore/developer/dashboard">upload your extension</a>
  /external/chromium_org/chrome/common/extensions/docs/templates/intros/
pushMessaging.html 22 field from manifest.json before you upload the app to the Chrome Web Store again.
  /external/chromium_org/chrome/common/metrics/
metrics_log_manager.h 83 // This is intended to be used when logs are being saved while an upload is in
84 // progress, in case the upload later succeeds.
155 // The text representations of the staged log, ready for upload to the server.
170 // This is necessary because during an upload there are two logs (staged
  /external/chromium_org/components/autofill/core/browser/
autofill_download_url.cc 44 return GURL(baseAutofillServiceUrl + "upload?client=" + kClientName);
form_structure.h 59 // Encodes the XML upload request from this FormStructure.
184 UPLOAD,
189 // it is a query or upload.
235 // Whether the server expects us to always upload, never upload, or default
236 // to the stored upload rates.
  /external/chromium_org/content/public/common/
file_chooser_params.h 28 // Like Open, but selects a folder for upload.
  /external/chromium_org/net/http/
http_request_info.h 43 // Any upload data.
  /external/chromium_org/net/url_request/
url_request_redirect_job.h 23 // the difference being that 302 converts POSTs to GETs and removes upload
  /external/chromium_org/third_party/WebKit/ManualTests/
post-multi-file-upload.html 24 This tests that the multi-file upload control works correctly. This test and the resources/multiFileResources must be placed on a web server so the test can be run manually.<br>
remove-input-file-onchange.html 15 <p><b>BUG ID:</b> <a href="rdar://problem/4621649">4621649</a> repro crash: Upload link causes crash on pages.google.com in Frame::nodeForWidget</p>
  /external/chromium_org/tools/
safely-roll-blink.py 51 help='(default) Put change in commit queue on upload.')
53 help='Don\'t put change in commit queue on upload.')
59 ' to upload. For instance, if you use the old git workflow,'
111 upload_cmd = ['git', 'cl', 'upload']
  /external/chromium_org/ui/resources/
PRESUBMIT.py 23 """Checks common to both upload and commit."""
  /frameworks/base/core/tests/bandwidthtests/src/com/android/bandwidthtest/util/
BandwidthTestUtil.java 123 * @param file {@link File} to upload
135 uri += "upload";
136 Log.d(LOG_TAG, "Upload url:" + uri);
148 Log.e(LOG_TAG, "Could not upload file with error: " + e);
  /frameworks/support/
build.gradle 36 task release(type: Upload) {
  /external/chromium_org/third_party/WebKit/Tools/TestResultServer/handlers/
testfilehandler.py 214 class Upload(webapp2.RequestHandler):
215 """Upload test results file to datastore."""
220 self.response.out.write("FAIL: missing upload file field.")
232 "Processing upload request, master: %s, builder: %s, test_type: %s.",
255 # FIXME: Upload full_results.json files for non-layout tests as well and stop supporting the
277 """Show a form so user can upload a file."""
281 "upload_url": "/testfile/upload",
  /docs/source.android.com/src/source/
submit-patches.jd 53 <p>Before you can upload to Gerrit, you need to establish a password that
95 <h2 id="upload-to-gerrit">Upload to gerrit</h2>
96 <p>Once you have committed your change to your personal history, upload it to gerrit with</p>
97 <pre><code>$ repo upload
99 <p>If you have started multiple branches in the same repository, you will be prompted to select which one(s) to upload.</p>
100 <p>After a successful upload, repo will provide you the URL of a new page on
110 <p>When you upload the amended patch, it will replace the original on gerrit and in your local git history.</p>
122 <p>After either automatic or manual rebase is complete, run <code>repo upload</code> to submit your rebased patch.</p>
182 <a href="/source/code-lines.html">Codelines, Branches, and Releases</a>. For most projects under <code>external/</code>, changes should be made upstream and then the Android maintainers informed of the new upstream release containing these changes. It may also be useful to upload patches that move us to track a new upstream release, though these can be difficult changes to mak (…)
    [all...]
using-repo.jd 88 <h2 id="upload">upload</h2>
89 <pre><code>repo upload [PROJECT_LIST]
94 configure an HTTPS password to enable upload authorization. Visit the
100 single commit, use git rebase -i before you run repo upload.</p>
101 <p>If you run repo upload without any arguments, it will search all the projects for changes to upload.</p>
108 <p>Use <code>repo upload --replace PROJECT</code> to open the change matching editor.</p>
115 [ 3022 ] c99883fe Teach 'repo upload --replace' how to add replacement patch se...
121 <p>After the upload is complete the changes will have an additional Patch Set.</p
    [all...]
  /external/chromium/chrome/browser/metrics/
histogram_synchronizer.h 21 // This class maintains state that is used to upload histogram data from the
25 // has changed since its last upload, and transmitting a pickled collection of
31 // log upload.
72 // Contact all renderers, and get them to upload to the browser any/all
78 // Contact all renderers, and get them to upload to the browser any/all
  /external/chromium_org/chrome/browser/policy/cloud/
device_management_service_browsertest.cc 64 const net::UploadDataStream* upload = request->get_upload(); local
65 if (upload != NULL &&
66 upload->element_readers().size() == 1 &&
67 upload->element_readers()[0]->AsBytesReader()) {
70 upload->element_readers()[0]->AsBytesReader();
  /external/chromium_org/content/browser/
histogram_synchronizer.h 24 // This class maintains state that is used to upload histogram data from the
28 // changed since its last upload, and transmitting a pickled collection of
34 // log upload.
65 // Contact all processes, and get them to upload to the browser any/all
69 // Contact all child processes, and get them to upload to the browser any/all
  /external/chromium_org/chrome/test/functional/ispy/ispy_core/tools/
rendering_test_manager_unittest.py 27 # Upload some images to the datastore.
41 # Upload some images to the datastore.
66 # Upload some tests to the datastore.
95 # Upload some tests to the datastore
156 # Upload a result
177 # Upload some tests.
  /external/bison/
README-release 41 corresponding upload-to destination in the emitted gnupload command.
59 make upload RELEASE='X.Y TYPE'
  /external/chromium/chrome/browser/autofill/
autofill_download_unittest.cc 48 // successful upload request, failed upload request.
212 // Set upload to 100% so requests happen.
245 // After that upload rates would be adjusted to 0.5/0.3
287 // Set upload to 0% so no new requests happen.
290 // No actual requests for the next two calls, as we set upload rate to 0%.
334 // Set upload to 100% so requests happen.
352 // Upload requests should be ignored for the next 10 seconds.
  /external/chromium_org/base/debug/
crash_logging.h 15 // These functions add metadata to the upload payload when sending crash reports
19 // the upload and are not included in the minidump!
  /external/chromium_org/chrome_frame/
metrics_service.cc 25 // that have been flagged for upload to the UMA server.
69 // The first UMA upload occurs after this interval.
72 // Default to one UMA upload per 10 mins.
82 // This class provides functionality to upload the ChromeFrame UMA data to the
119 NOTREACHED() << "Invalid upload data";
166 DLOG(ERROR) << "Failed to bind to upload data moniker. Error:"
332 // If this is the first uma upload by this process then subsequent uma
412 // If the user forbids uploading that's their business, and we don't upload

Completed in 1082 milliseconds

1 2 3 4 5 67 8 91011>>