diff options
| author | Jonathan Neuschäfer <j.neuschaefer@gmx.net> | 2011-08-20 17:02:58 +0200 |
|---|---|---|
| committer | Christopher Li <sparse@chrisli.org> | 2011-08-20 15:30:31 -0700 |
| commit | abca4fede1626676d783cc2178768cf08340ac9e (patch) | |
| tree | a849517a0f85303018b9eb6e81d6c4bb3a3ffd1c | |
| parent | d79064e7a3a36443a09d049eda0500d632d2a1a5 (diff) | |
| download | sparse-abca4fede1626676d783cc2178768cf08340ac9e.tar.gz | |
FAQ: fix a typo ("because or")
Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
Signed-off-by: Christopher Li <sparse@chrisli.org>
| -rw-r--r-- | FAQ | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -5,7 +5,7 @@ Q. Why not just use gcc? A. Gcc is big, complex, and the gcc maintainers are not interested in other uses of the gcc front-end. In fact, gcc has explicitly resisted splitting up the front and back ends and having some common - intermediate language because or religious license issues - you can + intermediate language because of religious license issues - you can have multiple front ends and back ends, but they all have to be part of gcc and licensed under the GPL. |