HomeSort by relevance Sort by last modified time
    Searched full:repository (Results 226 - 250 of 518) sorted by null

1 2 3 4 5 6 7 8 91011>>

  /sdk/sdkmanager/libs/sdkuilib/tests/com/android/sdkuilib/internal/repository/sdkman2/
PackagesDiffLogicTest.java 17 package com.android.sdkuilib.internal.repository.sdkman2;
19 import com.android.sdklib.internal.repository.BrokenPackage;
20 import com.android.sdklib.internal.repository.MockAddonPackage;
21 import com.android.sdklib.internal.repository.MockBrokenPackage;
22 import com.android.sdklib.internal.repository.MockEmptyPackage;
23 import com.android.sdklib.internal.repository.MockExtraPackage;
24 import com.android.sdklib.internal.repository.MockPlatformPackage;
25 import com.android.sdklib.internal.repository.MockPlatformToolPackage;
26 import com.android.sdklib.internal.repository.MockToolPackage;
27 import com.android.sdklib.internal.repository.Package
    [all...]
  /development/pdk/docs/source/
git-repo.jd 119 ]<br><br><div>Installs Repo in the current directory. This creates a .repo/ directory that contains Git repositories for the Repo source code and the standard Android manifest files. The .repo/ directory also containsmanifest.xml, which is a symlink to the selected manifest in the .repo/manifests/ directory.<br><br>The -u argument specifies a URL from which to retrieve a manifest repository. For example:<br>$ repo init -u git://android.git.kernel.org/platform/manifest.git <br><br>To select a manifest file within the repository, use the -m option. (If no manifest name is selected, the default is default.xml.)For example:<br>$ repo init -u git://android.git.kernel.org/platform/manifest.git-m dalkvik-plus.xml <br><br>To specify a revision, that is, a particular manifest-branch, use the -b option. For example:<br>$ repo init -u git://android.git.kernel.org/platform/manifest.git-b release-1.0<br><br>To see other repo init options, run <br>$ repo help init <br><br><b>Note:</b>
125 ]<br><br><div>Downloads new changes and updates the working files in your local environment. After a successful repo sync, the code in specified projects will be up to date with the code in the remote repository.<br><br>You can specify project-list as a list of names or a list of paths to local source directories for the projects:<br>repo sync [<i>proj1</i>
134 <ol><li>If the project has never been synchronized, then repo sync is equivalent to git clone. All branches in the remote repository are copied to the local project directory.
138 is the currently checked-out branch in the local project directory. If the local branch is not tracking a branch in the remote repository, then no synchronization will occur for the project.<br><br>If the git rebase operation results in merge conflicts, you will need to use the normal Git commands (for example, git rebase --continue) to resolve the conflicts.<br></li>
  /sdk/eclipse/plugins/com.android.ide.eclipse.adt/META-INF/
MANIFEST.MF 129 com.android.sdklib.internal.repository;x-friends:="com.android.ide.eclipse.tests",
130 com.android.sdklib.repository;x-friends:="com.android.ide.eclipse.tests",
134 com.android.sdkuilib.internal.repository;x-friends:="com.android.ide.eclipse.tests",
135 com.android.sdkuilib.internal.repository.icons;x-friends:="com.android.ide.eclipse.tests",
138 com.android.sdkuilib.repository;x-friends:="com.android.ide.eclipse.tests",