From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: What is a good way to get comments on patches for bug tracker bugs?
Date: Sun, 06 Jan 2008 17:08:08 +0000 [thread overview]
Message-ID: <1199639288.4658.18.camel@localhost.localdomain> (raw)
In-Reply-To: <477FB6E5.9030507@opensimpad.org>
On Sat, 2008-01-05 at 17:57 +0100, Bernhard Guillon wrote:
> I'd like to know what could be a good way to get comments on patches
> which have been attached to bugtracker bugs.
> Is there some special marking to set or should someone ask on the
> mailing list/IRC about a comment?
The best thing to do would be to mention the bug numbers here and/or on
irc and hopefully someone will have a look. At the very least I'll try
and tell you who might be the person(s) who needs to review them if I
know which bugs they are...
Cheers,
Richard
next prev parent reply other threads:[~2008-01-06 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 16:57 What is a good way to get comments on patches for bug tracker bugs? Bernhard Guillon
2008-01-06 17:08 ` Richard Purdie [this message]
2008-01-06 21:30 ` Bernhard Guillon
2008-01-07 19:40 ` Rolf Leggewie
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=1199639288.4658.18.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.