TODO update
Junio C Hamano committed
May 18, 2007 at 22:52 UTC
f8a7774f13df2954ce27b218490f83443e51748e
1 file changed
+37
TODO
+37
@@ -142,6 +142,43 @@ Technical (milder)
142
Technical (trivial)
143
-------------------
144
145
+* Change the "first line of commit message is special" rule to
146
+ "first paragraph" and then wrap it.
147
+
148
+ From: Junio C Hamano <junkio@cox.net>
149
+ Message-ID: <7vsla5pkug.fsf@assigned-by-dhcp.cox.net>
150
+
151
+ This is slightly related, but I have been wondering about the
152
+ interaction with "single-liner summary, empty line and then the
153
+ rest" convention and various commands in the log family.
154
+
155
+ Currently, --pretty=oneline and --pretty=email (hence format-patch)
156
+ take and use only the first line. I think we could change it to:
157
+
158
+ - take the first paragraph, where the definition of the first
159
+ paragraph is "skip all blank lines from the beginning, and
160
+ then grab everything up to the next empty line".
161
+
162
+ - replace all line breaks with a whitespace.
163
+
164
+ This change would not affect well-behaved commit messages that
165
+ adhere to the convention, as their first paragraph always
166
+ consist of a single line. On the other hand, people from
167
+ different culture can get frustrated by their commit message
168
+ chomped at the first linebreak in the middle of sentence right
169
+ now, which would be helped by this change.
170
+
171
+ Their Subject: and --pretty=oneline output would become very
172
+ long and unsightly, but their commit messages are already
173
+ ugly anyway, and such a change at least avoid the loss of
174
+ information.
175
+
176
+ If we were to do this, Subject: line would most likely use
177
+ RFC2822 line folding at the places where line breaks were in the
178
+ original, but that goes without saying.
179
+
180
+ What do people think?
181
+
182
* Give --stdin to git-log, similar to git-rev-list
183
184
From: "Marco Costalba" <mcostalba@gmail.com>