From 66286e9e61d18c04451865922097852a3792e5be Mon Sep 17 00:00:00 2001
From: Misha Brukman
Date: Thu, 11 Dec 2008 19:44:51 +0000
Subject: [PATCH] * Removed stray
tag * Whitespace cleanups
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@60891 91177308-0d34-0410-b5e6-96231b3b80d8
---
docs/DeveloperPolicy.html | 12 +++++-------
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html
index 6ea772407eb..c2b1ca13267 100644
--- a/docs/DeveloperPolicy.html
+++ b/docs/DeveloperPolicy.html
@@ -91,8 +91,8 @@
-
When making a patch for review, the goal is to make it as easy for the
- reviewer to read it as possible. As such, we recommend that you:
+
When making a patch for review, the goal is to make it as easy for the
+ reviewer to read it as possible. As such, we recommend that you:
- Make your patch against the Subversion trunk, not a branch, and not an
old version of LLVM. This makes it easy to apply the patch.
@@ -102,14 +102,13 @@
the time the patch was created and the time it is applied.
- Patches should be made with this command:
-
svn diff -x -u
- or with the utility utils/mkpatch, which makes it easy to read the
- diff.
+
+ or with the utility utils/mkpatch, which makes it easy to read the
+ diff.
- Patches should not include differences in generated code such as the
code generated by flex, bison or tblgen. The
utils/mkpatch utility takes care of this for you.
-
When sending a patch to a mailing list, it is a good idea to send it as an
@@ -124,7 +123,6 @@
Content-Disposition: inline rather than Content-Disposition:
attachment. Apple Mail gamely displays such a file inline, making it
difficult to work with for reviewers using that program.
-