Revision: 25157
Author: [email protected]
Date: Wed Nov 5 14:08:10 2014 UTC
Log: Edited wiki page UsingGit through web user interface.
https://code.google.com/p/v8/source/detail?r=25157
Modified:
/wiki/UsingGit.wiki
=======================================
--- /wiki/UsingGit.wiki Thu Oct 30 08:17:53 2014 UTC
+++ /wiki/UsingGit.wiki Wed Nov 5 14:08:10 2014 UTC
@@ -1,237 +1,1 @@
-#summary This page describes how to use the Git mirror of the V8
repository.
-
-= Git repository =
-
-V8's trunk and bleeding_edge branches are mirrored to git at
https://chromium.googlesource.com/v8/v8.git
-
-V8's bleeding_edge branch has also an official git mirror on github:
http://github.com/v8/v8-git-mirror.
-
-== Prerequisites ==
-
-Make sure {{{git}}} and {{{git-svn}}} are installed. To install using
{{{apt-get}}}:
-{{{
-apt-get install git git-svn
-}}}
-
-You will also need to
[http://dev.chromium.org/developers/how-tos/install-depot-tools install
depot tools].
-
-== How to start ==
-
-Make sure depot_tools are up-to-date by typing once:
-
-{{{
-gclient
-}}}
-
-
-Cloning v8's branches, setting up git svn, and getting all dependencies
can be done using:
-
-{{{
-fetch v8
-cd v8
-}}}
-
-After that you're intentionally in a detached head state.
-
-Optionally you can specify how new branches should be tracked:
-
-{{{
-git config branch.autosetupmerge always
-}}}
-
-Alternatively, you can create new local branches like this (recommended):
-
-{{{
-git new-branch mywork
-}}}
-
-== Staying up-to-date ==
-
-Update your current branch with git pull. Note that if you're not on a
branch, git pull won't work, and you'll need to use git fetch instead.
-
-{{{
-git pull
-}}}
-
-Sometimes dependencies of v8 are updated. You can synchronize those by
running
-
-{{{
-gclient sync
-}}}
-
-== Sending code for reviewing ==
-
-First, you need to configure [http://neugierig.org/software/git/?r=git-cl
git-cl], thankfully it’s done magically by a single command:
-
-{{{
-git cl config http://v8.googlecode.com/svn
-}}}
-
-Then do
-
-{{{
-git cl upload
-}}}
-
-== Committing ==
-
-Update your branch:
-
-{{{
-git pull --rebase origin
-}}}
-
-Then commit using
-
-{{{
-git cl dcommit
-}}}
-
-== Troubleshooting ==
-
-In case of svn problems on dcommit, you can try the following to get back
to a clean state:
-
-{{{
-rm -rf .git/svn
-git svn fetch
-}}}
-
-= Post Git migration =
-
-The following becomes first important after the v8 git migration.
-
-== Git credentials setup for committers (.netrc file) ==
-
-If you want to push commits directly to Git you need to setup .netrc file
with your git password:
-
- # Go to https://chromium.googlesource.com/new-password - login with your
@chromium.org account (e.g. your committer account, non-chromium.org ones
work too). Note: creating a new password doesn't automatically revoke any
previously created passwords.
- # Follow the instructions in the "Staying Authenticated" section. It
would ask you to copy-paste two lines into ~/.netrc file.
- # In the end, ~/.netrc should have two lines that look like:
-
-{{{
-machine chromium.googlesource.com login git-yourusername.chromium.org
password <generated pwd>
-machine chromium-review.googlesource.com login
git-yourusername.chromium.org password <generated pwd>
-}}}
-
-Make sure that ~/.netrc file's permissions are 0600 as many programs
refuse to read .netrc files which are readable by anyone other than you.
-
-= For project members =
-
-
-== Try jobs ==
-
-=== Creating a try job from codereview ===
-
- # Upload a CL to rietveld.
-{{{
-git cl upload
-}}}
- # Try the CL by sending a try job to the try bots like this:
-{{{
-git cl try
-}}}
- # Wait for the try bots to build and you will get an e-mail with the
result. You can also check the try state at your patch on codereview.
- # If applying the patch fails you either need to rebase your patch or
specify the v8 revision to sync to:
-{{{
-git cl try --revision=1234
-}}}
-
-=== Creating a try job from a local branch ===
-
- # Commit some changes to a git branch in the local repo.
- # Try the change by sending a try job to the try bots like this:
-{{{
-git try
-}}}
- # Wait for the try bots to build and you will get an e-mail with the
result. Note: There are issues with some of the slaves at the moment.
Sending try jobs from codereview is recommended.
-
-=== Useful arguments ===
-
-The revision argument tells the try bot what revision of the code base
will be used for applying your local changes to. Without the revision, our
LKGR revision is used as the base ([http://v8-status.appspot.com/lkgr]).
-{{{
-git try --revision=1234
-}}}
-To avoid running your try job on all bots, use the --bot flag with a
comma-separated list of builder names. Example:
-{{{
-git try --bot=v8_mac_rel
-}}}
-
-=== Viewing the try server ===
-
-http://build.chromium.org/p/tryserver.v8/waterfall
-
-=== Access credentials ===
-
-If asked for access credentials, use your @chromium.org email address and
your generated password from [http://code.google.com/hosting/settings
googlecode.com].
-
-== Full SVN checkout (deprecated) ==
-
-This section describes an alternate way to get the source code. Following
these instructions makes sure you'll get a clone of the full SVN repository
including all branches and history. You'll need this to perform pushes to
trunk.
-
- # Make sure you have git and git-svn installed.
- # Fetch the sources:
- {{{
-git svn clone --stdlayout --branches=branches/experimental
--branches=branches --prefix=svn/ [email protected]
https://v8.googlecode.com/svn v8.git
- }}}
- This process takes a loooong time (a few hours). It might fail at some
point; if it does you can use the following command to tell it to continue
where it left off:
- {{{
-git svn fetch
- }}}
- # Make sure you're on the `master` branch and switch its svn parent to
bleeding_edge:
-{{{
-git reset --hard svn/bleeding_edge
-}}}
- # [http://dev.chromium.org/developers/how-tos/install-depot-tools
Install depot tools] and put them in your `$PATH`
- You might want to edit your `~/.bashrc` to set up that `$PATH` on
subsequent logins.
- # Configure `git-cl`:
- {{{
-git cl config http://v8.googlecode.com/svn
- }}}
- # Install required dependencies:
- {{{
-make dependencies
- }}}
-
-== Staying up to date (deprecated) ==
-
-{{{
-git checkout master
-git svn rebase
-git rebase master your_feature_branch
-}}}
-
-If any of the build dependencies has changed, you might have to update
them:
-
-{{{
-make dependencies
-}}}
-
-== Sending code for reviewing (deprecated) ==
-
-First, you need to configure [http://neugierig.org/software/git/?r=git-cl
git-cl], thankfully it’s done magically by a single command:
-
-{{{
-git cl config http://v8.googlecode.com/svn
-}}}
-
-Then do
-
-{{{
-git cl upload
-}}}
-
-== Committing (deprecated) ==
-
-Update your branch using git-svn:
-
-{{{
-git svn rebase
-}}}
-
-Then commit using
-
-{{{
-git cl dcommit
-}}}
-
-*Do not use <font color=red>`git svn dcommit`</font> for committing*, as
it lacks git-cl's magic. Pro tip: you can use `git cl rebase` for updating
(it's an alias for `git svn rebase`), so you'll never have to use any `git
svn ...` command at all.
+This page has moved to https://code.google.com/p/v8-wiki/wiki/UsingGit
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
