From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ed Bartosh <ed.bartosh@linux.intel.com>,
bitbake-devel@lists.openembedded.org
Cc: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: [PATCH 0/3] Fix SDK downloads forbuilds
Date: Mon, 18 Jan 2016 22:09:27 +0000 [thread overview]
Message-ID: <1453154967.27999.93.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1453124453.git.ed.bartosh@linux.intel.com>
On Mon, 2016-01-18 at 15:45 +0200, Ed Bartosh wrote:
> Elliot Smith (3):
> toaster: toasterui: listen for bb.event.MetadataEvent
> toaster: toasterui: log OSErrorException metadata events
> toaster: toastergui: make artifact download more robust
Its a small detail but when sending patches, "toasterui:" is fine in
the shortlog, we don't need "toaster: toasterui:". The idea is to
highlight which bit of the system is being changed and "toasterui"
conveys that fine.
[cc'd to the toaster list so everyone sees this]
No need to resend these, I just tweaked the lines.
Cheers,
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ed Bartosh <ed.bartosh@linux.intel.com>,
bitbake-devel@lists.openembedded.org
Cc: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: [bitbake-devel] [PATCH 0/3] Fix SDK downloads forbuilds
Date: Mon, 18 Jan 2016 22:09:27 +0000 [thread overview]
Message-ID: <1453154967.27999.93.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1453124453.git.ed.bartosh@linux.intel.com>
On Mon, 2016-01-18 at 15:45 +0200, Ed Bartosh wrote:
> Elliot Smith (3):
> toaster: toasterui: listen for bb.event.MetadataEvent
> toaster: toasterui: log OSErrorException metadata events
> toaster: toastergui: make artifact download more robust
Its a small detail but when sending patches, "toasterui:" is fine in
the shortlog, we don't need "toaster: toasterui:". The idea is to
highlight which bit of the system is being changed and "toasterui"
conveys that fine.
[cc'd to the toaster list so everyone sees this]
No need to resend these, I just tweaked the lines.
Cheers,
Richard
next prev parent reply other threads:[~2016-01-18 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 13:45 [PATCH 0/3] Fix SDK downloads forbuilds Ed Bartosh
2016-01-18 13:45 ` [PATCH 1/3] toaster: toasterui: listen for bb.event.MetadataEvent Ed Bartosh
2016-01-18 13:45 ` [PATCH 2/3] toaster: toasterui: log OSErrorException metadata events Ed Bartosh
2016-01-18 13:45 ` [PATCH 3/3] toaster: toastergui: make artifact download more robust Ed Bartosh
2016-01-18 22:09 ` Richard Purdie [this message]
2016-01-18 22:09 ` [bitbake-devel] [PATCH 0/3] Fix SDK downloads forbuilds 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=1453154967.27999.93.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=ed.bartosh@linux.intel.com \
--cc=toaster@yoctoproject.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.