From: Junqian Gordon Xu <xjqian@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev - Ignore false toggle signals (work-around for OE#3390).
Date: Wed, 20 Feb 2008 21:34:43 -0500 [thread overview]
Message-ID: <47BCE343.7060600@gmail.com> (raw)
In-Reply-To: <20080220155339.67aed5d4@widy.localdomain>
On 02/20/2008 08:53 AM, Paul Sokolovsky wrote:
> It practice that means that developers should annotate the bug with
> "pushed to .dev", "RFCed for merging to stable", "pushed to stable",
> and ultimately, "package in feed, closing".
I prefer this approach to opening a separate dup ticket. If we can
streamline the process of "RFCed for merging to stable" and "package in
feed", we only need the "pushed to .dev" and/or "pushed to stable" as
sufficient landmarks for closing a bug.
IMHO, whatever definition for closing a bug is not that much a big deal.
Instead we should focus on how to streamline the process of getting
fixes from .dev ---> feed.
Regards
Gordon
prev parent reply other threads:[~2008-02-21 2:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1JRbhB-0000nu-DN@linuxtogo.org>
2008-02-19 23:58 ` [oe-commits] org.oe.dev - Ignore false toggle signals (work-around for OE#3390) Paul Sokolovsky
2008-02-20 0:04 ` Paul Sokolovsky
2008-02-20 10:15 ` Stanislav Brabec
2008-02-20 13:53 ` Paul Sokolovsky
2008-02-20 18:38 ` what is a fixed bug? (was: [oe-commits] org.oe.dev - Ignore false toggle signals (work-around for OE#3390).) Rolf Leggewie
2008-02-20 19:26 ` Paul Sokolovsky
2008-02-21 10:57 ` what is a fixed bug? Rolf Leggewie
2008-02-21 12:04 ` Paul Sokolovsky
2008-02-21 12:40 ` Rolf Leggewie
2008-02-21 13:11 ` Paul Sokolovsky
2008-02-21 14:23 ` Rolf Leggewie
2008-02-21 2:34 ` Junqian Gordon Xu [this message]
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=47BCE343.7060600@gmail.com \
--to=xjqian@gmail.com \
--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.