Revision bce0d923 doc/developer.texi

View differences:

doc/developer.texi
180 180
   Always fill out the commit log message. Describe in a few lines what you
181 181
   changed and why. You can refer to mailing list postings if you fix a
182 182
   particular bug. Comments such as "fixed!" or "Changed it." are unacceptable.
183
   Recommanded format:
184
   area changed: Short 1 line description
185

  
186
   details describing what and why and giving references.
183 187
@item
184
   If you apply a patch by someone else, include the name and email address in
185
   the log message. Since the ffmpeg-cvslog mailing list is publicly
186
   archived you should add some SPAM protection to the email address. Send an
188
   Make sure the author of the commit is set correctly. (see git commit --author)
189
   If you apply a patch, send an
187 190
   answer to ffmpeg-devel (or wherever you got the patch from) saying that
188 191
   you applied the patch.
189 192
@item
......
243 246

  
244 247
First, read the (@pxref{Coding Rules}) above if you did not yet.
245 248

  
246
When you submit your patch, try to send a unified diff (diff '-up'
247
option). We cannot read other diffs :-)
249
When you submit your patch, please use @code{git format-patch} or
250
@code{git send-email}. We cannot read other diffs :-)
248 251

  
249 252
Also please do not submit a patch which contains several unrelated changes.
250 253
Split it into separate, self-contained pieces. This does not mean splitting

Also available in: Unified diff