1 file changed, 3 insertions, 5 deletions

diff --git a/source/ui-patch.c b/source/ui-patch.cindex ef63d00..bc98f2e 100644--- a/source/ui-patch.c+++ b/source/ui-patch.c@@ -1,11 +1,9 @@ /*  * The patch page, which serves a commit or a range of commits as plain text  * in the mail format git format-patch writes, so that a change read in cgit- * can be fed straight to git am. It is one of the repository commands in- * cmd.c, taking the newer revision from id, the older one from id2, and an- * optional path that narrows the diff. A merge carries no single patch and so- * drops out of a range, and max-patch-count bounds how many commits one- * request may emit.+ * can be fed straight to git am. A merge carries no single patch and drops+ * out of a range, and max-patch-count bounds how many commits one request+ * may emit.  */  #define USE_THE_REPOSITORY_VARIABLE
diff --git a/source/ui-patch.c b/source/ui-patch.c
index ef63d00..bc98f2e 100644
--- a/source/ui-patch.c
+++ b/source/ui-patch.c
@@ -1,11 +1,9 @@
 /*
  * The patch page, which serves a commit or a range of commits as plain text
  * in the mail format git format-patch writes, so that a change read in cgit
- * can be fed straight to git am. It is one of the repository commands in
- * cmd.c, taking the newer revision from id, the older one from id2, and an
- * optional path that narrows the diff. A merge carries no single patch and so
- * drops out of a range, and max-patch-count bounds how many commits one
- * request may emit.
+ * can be fed straight to git am. A merge carries no single patch and drops
+ * out of a range, and max-patch-count bounds how many commits one request
+ * may emit.
  */
 
 #define USE_THE_REPOSITORY_VARIABLE