From: Jesse Gilles <jgilles@multitech.com>
To: openembedded-devel@lists.openembedded.org
Cc: Paul Menzel <paulepanter@users.sourceforge.net>
Subject: Re: [2011.03-maintenance] do_compile failed for cacao_0.99.3.bb
Date: Wed, 31 Aug 2011 09:25:41 -0500 [thread overview]
Message-ID: <1314800741.17073.7.camel@jjg-linux> (raw)
In-Reply-To: <4E5DDBBE.4050007@dresearch-fe.de>
On Wed, 2011-08-31 at 08:59 +0200, Steffen Sledz wrote:
> Mea culpa. I should have asked the contributor to resend the patch
> with a policy conforming comment. Sorry.
>
> Do we still have a chance to change the comment if the patch was
> already pushed?
>
> Steffen
Yes, sorry about this, I wasn't aware that discussing a patch on the
list and having it in the body of an email would automatically pull it
into patchwork when I did it. I didn't really intend for it to get
committed as-is (comments-wise anyway) since I was more trying to
discuss the patch rather than submit it with proper comments, etc.
Thanks Steffen for taking initiative though :)
I don't think you can change the comment once it is in the shared OE
repo (and therefore in repos on other peoples machines). You could
revert it and resubmit with a better comment though. Please correct me
if I'm wrong on this...
Jesse
next prev parent reply other threads:[~2011-08-31 14:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 12:13 [2011.03-maintenance] do_compile failed for cacao_0.99.3.bb Steffen Sledz
2011-08-19 14:30 ` Steffen Sledz
2011-08-23 7:28 ` Steffen Sledz
2011-08-23 7:35 ` Robert Schuster
2011-08-23 7:49 ` Steffen Sledz
2011-08-23 17:16 ` George C. Huntington, III
2011-08-24 15:22 ` Jesse Gilles
2011-08-24 17:40 ` Tom Rini
2011-08-24 18:25 ` Koen Kooi
2011-08-25 10:59 ` Steffen Sledz
2011-08-25 14:09 ` Steffen Sledz
2011-08-30 10:51 ` Steffen Sledz
2011-08-30 12:30 ` Paul Menzel
2011-08-30 15:25 ` George C. Huntington, III
2011-08-31 6:59 ` Steffen Sledz
2011-08-31 14:25 ` Jesse Gilles [this message]
2011-08-31 6:51 ` Robert Schuster
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=1314800741.17073.7.camel@jjg-linux \
--to=jgilles@multitech.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paulepanter@users.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox