From e36291a1ef834e83089d52cd3129aa5dd666e3cb Mon Sep 17 00:00:00 2001 From: Renato Golin Date: Sun, 6 Jan 2013 00:14:27 +0000 Subject: Add reference to dcommit on GettingStarted Signed-off-by: Renato Golin git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@171642 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/GettingStarted.rst | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) (limited to 'docs/GettingStarted.rst') diff --git a/docs/GettingStarted.rst b/docs/GettingStarted.rst index 3605686f16..443d21f04a 100644 --- a/docs/GettingStarted.rst +++ b/docs/GettingStarted.rst @@ -633,8 +633,21 @@ upstream git repo, run: This leaves your working directories on their master branches, so you'll need to ``checkout`` each working branch individually and ``rebase`` it on top of its -parent branch. (Note: This script is intended for relative newbies to git. If -you have more experience, you can likely improve on it.) +parent branch. + +To commit back changes via git-svn, use ``dcommit``: + +.. code-block:: console + + % git svn dcommit + +Note that git-svn will create one SVN commit for each Git commit you have pending, +so squash and edit each commit before executing ``dcommit`` to make sure they all +conform to the coding standards and the developers' policy. + +On success, ``dcommit`` will rebase against the HEAD of SVN, so to avoid conflict, +please make sure your current branch is up-to-date (via fetch/rebase) before +proceeding. The git-svn metadata can get out of sync after you mess around with branches and ``dcommit``. When that happens, ``git svn dcommit`` stops working, complaining @@ -645,6 +658,8 @@ about files with uncommitted changes. The fix is to rebuild the metadata: % rm -rf .git/svn % git svn rebase -l +Please, refer to the Git-SVN manual (``man git-svn``) for more information. + Local LLVM Configuration ------------------------ -- cgit v1.2.3