Revision: 5863
Author: mikhail.naganov
Date: Fri Nov 19 04:21:09 2010
Log: Added section about faster SVN updates
http://code.google.com/p/v8/source/detail?r=5863
Modified:
/wiki/UsingGit.wiki
=======================================
--- /wiki/UsingGit.wiki Wed Aug 19 02:42:47 2009
+++ /wiki/UsingGit.wiki Fri Nov 19 04:21:09 2010
@@ -22,20 +22,6 @@
git checkout <your-development-branch>
git rebase master
}}}
-
-== Tracking SVN changes ==
-
-{{{
-git update-ref refs/remotes/trunk origin/master
-git svn init -T branches/bleeding_edge http://v8.googlecode.com/svn
-git svn fetch
-}}}
-
-Now you can also update your branch using git-svn:
-
-{{{
-git svn rebase
-}}}
== Sending code for reviewing ==
@@ -45,11 +31,19 @@
git cl config http://v8.googlecode.com/svn
}}}
-Then use `git cl upload` command.
+Then do
+
+{{{
+git cl upload
+}}}
= For project members =
-Project members do use `https://` prefix when accessing SVN, so git-svn
generates different commit object for them. To overcome this, we have
another branch called `bleeding_edge`. So, setting up SVN tracking differs
a bit:
+== Tracking SVN changes ==
+
+Project members do use `https://` prefix when accessing SVN.
+We have a branch called `bleeding_edge`. Setting up SVN tracking
+looks like this:
{{{
git update-ref refs/remotes/trunk origin/bleeding_edge
@@ -57,7 +51,25 @@
git svn fetch
git branch bleeding_edge origin/bleeding_edge
}}}
+
+For faster updates, tweak up your `.git/config`: update the
`[svn-remote "svn"]` section like this:
+
+{{{
+[svn-remote "svn"]
+ url = https://v8.googlecode.com/svn
+ fetch = branches/bleeding_edge:refs/remotes/origin/bleeding_edge
+}}}
== Committing ==
-Should just work using `git cl dcommit`.
+Update your branch using git-svn:
+
+{{{
+git svn rebase
+}}}
+
+Then commit using
+
+{{{
+git cl dcommit
+}}}
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
