All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 8/8] libx11: enable xcb support
Date: Fri, 08 Jul 2011 14:57:53 +0100	[thread overview]
Message-ID: <1310133474.6337.116.camel@phil-desktop> (raw)
In-Reply-To: <0a996270e51deae8b1f22299e1e024dcb6c0be88.1310081443.git.sgw@linux.intel.com>

On Thu, 2011-07-07 at 16:31 -0700, Saul Wold wrote:
> [YOCTO #1196]
> 
> Signed-off-by: Saul Wold <sgw@linux.intel.com>

We seem to be seeing quite a lot of patches recently whose long-form
comment consists of a Yocto bug number, S-O-B line and nothing else.
That might be fine for the most notorious bugs, where even non-Yocto
people would immediately recognise the number, but in general it's a bit
tedious to keep having to go to the Yocto bugzilla to find out what the
patch is trying to do.  Would it be possible to get a slightly more
descriptive commit message for future changes?

See also the fine guidelines from our helpful TSC:

http://wiki.openembedded.org/index.php/Commit_Patch_Message_Guidelines

thanks

p.





  reply	other threads:[~2011-07-08 14:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07 23:31 [PATCH 0/8] Bug Fixes for M2 Rc2 Saul Wold
2011-07-07 23:31 ` [PATCH 1/8] rootfs_rpm: Add 50Meg to image size for zypper Saul Wold
2011-07-07 23:38   ` Richard Purdie
2011-07-08  5:42     ` Saul Wold
2011-07-08 14:52       ` Richard Purdie
2011-07-07 23:31 ` [PATCH 2/8] image.bbclass: add LINGUAS_INSTALL to depends list Saul Wold
2011-07-07 23:31 ` [PATCH 3/8] gnome-doc-utils: Add RDEPENDS on bash Saul Wold
2011-07-07 23:31 ` [PATCH 4/8] quilt: " Saul Wold
2011-07-07 23:31 ` [PATCH 5/8] console-tools: " Saul Wold
2011-07-07 23:31 ` [PATCH 6/8] usbutils: " Saul Wold
2011-07-08  7:28   ` Koen Kooi
2011-07-08 15:42     ` Richard Purdie
2011-07-07 23:31 ` [PATCH 7/8] eglibc: " Saul Wold
2011-07-08  0:59   ` Khem Raj
2011-07-08  1:15     ` Saul Wold
2011-07-08  5:27       ` Khem Raj
2011-07-12 13:38         ` Phil Blundell
2011-07-08  6:53   ` Frans Meulenbroeks
2011-07-08  7:01     ` Koen Kooi
2011-07-08  7:23       ` Frans Meulenbroeks
2011-07-07 23:31 ` [PATCH 8/8] libx11: enable xcb support Saul Wold
2011-07-08 13:57   ` Phil Blundell [this message]
2011-07-18 22:55   ` Martin Jansa
2011-07-08  6:49 ` [PATCH 0/8] Bug Fixes for M2 Rc2 Frans Meulenbroeks
2011-07-08 15:41 ` Richard Purdie

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=1310133474.6337.116.camel@phil-desktop \
    --to=pb@pbcl.net \
    --cc=openembedded-core@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.