All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: openembedded-devel@lists.openembedded.org
Subject: OEDEM 2010: [RFC] useful commit message
Date: Fri, 29 Oct 2010 11:02:49 +0200	[thread overview]
Message-ID: <1288342969.18134.5.camel@mattotaupa> (raw)

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

Dear OE folks,


could you please discuss the following proposal.

I would very much like more elaborate commit messages. This is in my
opinion already demanded by the commit policy [1], but often patch
submitters, especially those not sending changes to review to the list,
since they have direct access to the repository, fail to adhere to the
policy.

The reason is, quite often I do not understand why a change was
necessary. It would very much help me, if at least the error message was
pasted to be able to compare with one’s own error messages and what
distribution and machine was used to test the recipe.

I added an item to the OEDEM wiki page too [2].


Thanks,

Paul


[1] http://wiki.openembedded.org/index.php/Commit_Policy
[2] http://wiki.openembedded.org/index.php?title=Oedem%2F2010&diff=2961&oldid=2954

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

             reply	other threads:[~2010-10-29  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29  9:02 Paul Menzel [this message]
2010-10-29 10:45 ` OEDEM 2010: [RFC] useful commit message Frans Meulenbroeks
2010-10-31 10:20 ` Koen Kooi
2010-11-01 19:36   ` Denys Dmytriyenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1288342969.18134.5.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.