X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FGettingStarted.html;h=0a6a4811880ebc2145514e8abb955d3e9807cd7f;hb=39fe397421a23ea44e19b991e64b04f335f7bde6;hp=5e1985ef132f0fea62c35f0d45c1472f62c4acfc;hpb=24ad111a05b9d0e60a79c4f915bf1bb1d24db40b;p=oota-llvm.git diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index 5e1985ef132..0a6a4811880 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -516,9 +516,8 @@ href="GCCFEBuildInstrs.html">try to compile it on your platform.
LLVM is very demanding of the host C++ compiler, and as such tends to expose
bugs in the compiler. In particular, several versions of GCC crash when trying
-to compile LLVM. We routinely use GCC 3.3.3, 3.4.0, and Apple 4.0.1
-successfully with them (however, see important notes below). Other versions
-of GCC will probably work as well. GCC versions listed
+to compile LLVM. We routinely use GCC 4.2 (and higher) or Clang.
+Other versions of GCC will probably work as well. GCC versions listed
here are known to not work. If you are using one of these versions, please try
to upgrade your GCC to something more recent. If you run into a problem with a
version of GCC not listed here, please let
@@ -814,6 +813,88 @@ cd llvm/tools
git clone http://llvm.org/git/clang.git
+
+Since the upstream repository is in Subversion, you should use
+"git pull --rebase"
+instead of "git pull" to avoid generating a non-linear
+history in your clone.
+To configure "git pull" to pass --rebase by default
+on the master branch, run the following command:
+
+Please read Developer Policy, too.
+
+Assume master points the upstream and mybranch points your
+working branch, and mybranch is rebased onto master.
+At first you may check sanity of whitespaces:
+
+The easiest way to generate a patch is as below:
+
+It is a little different from svn-generated diff. git-diff-generated diff has
+prefixes like a/ and b/. Don't worry, most developers might
+know it could be accepted with patch -p1 -N.
+
+But you may generate patchset with git-format-patch. It generates
+by-each-commit patchset. To generate patch files to attach to your article:
+
+If you would like to send patches directly, you may use git-send-email or
+git-imap-send. Here is an example to generate the patchset in Gmail's [Drafts].
+
+Then, your .git/config should have [imap] sections.
+
+git config branch.master.rebase true
+
+
+Sending patches with Git
+
+git diff --check master..mybranch
+
+
+
+git diff master..mybranch > /path/to/mybranch.diff
+
+
+
+git format-patch --no-attach master..mybranch -o /path/to/your/patchset
+
+
+
+git format-patch --attach master..mybranch --stdout | git imap-send
+
+
+
+[imap]
+ host = imaps://imap.gmail.com
+ user = your.gmail.account@gmail.com
+ pass = himitsu!
+ port = 993
+ sslverify = false
+; in English
+ folder = "[Gmail]/Drafts"
+; example for Japanese, "Modified UTF-7" encoded.
+ folder = "[Gmail]/&Tgtm+DBN-"
+; example for Traditional Chinese
+ folder = "[Gmail]/&g0l6Pw-"
+
+
+For developers to work with git-svn