From: Alex Schuilenburg <alexs@ecoscentric.com>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] adding a package with configtool fails - new stuff
Date: Sun, 24 Mar 2013 21:57:00 -0000 [thread overview]
Message-ID: <514F76D0.7090604@ecoscentric.com> (raw)
In-Reply-To: <514B5F0D.6070307@gmail.com>
Bob,
On 21/03/2013 19:27, Bob Brusa wrote:
> Am 21.03.2013 20:12, schrieb Bob Brusa:
>> Hi,
>> I few days ago, I rised a bug report on bugzille on the above subject.
>> Now I checked again its status, found a Comment 5 by John Dallaway and
>> added a new Comment 6 and stored it.
>>
>> Result: Ifound myself in a very old bug report I had entered in 2008 -
>> and the new one is no longer listed under my reports - Just the old
>> ones. I cannot retreave it.....
>> Regards - Bob.
>>
>>
> More strange things: I was able to retreave my report 1001798 using
> keywords. I quickly checked it: My new comment is there. I close it
> and click on My Requests and now, not a single report is displayed.
> All vanished....
What you describe seems fine to me. Are you perhaps confusing "My
Requests" with "My Bugs"? The former will list bugs where you have set
a request (e.g. for a patch review), while the latter will list bugs you
have reported.
Also, when you select a bug from within a search (e.g. "My bugs" or
"Open bugs" from front page), if you update the bug with a comment or
similar, bugzilla will automatically open the next bug in your search
list. The order of the list is whatever you last set it.
-- Alex
I am guessing you are talking about the "Open bugs" from on the front
page of bugzilla.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2013-03-24 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 19:12 Bob Brusa
2013-03-21 19:27 ` Bob Brusa
2013-03-24 21:57 ` Alex Schuilenburg [this message]
2013-03-27 14:03 ` Bob Brusa
2013-03-27 14:27 ` Alex Schuilenburg
2013-03-27 16:57 ` Bob Brusa
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=514F76D0.7090604@ecoscentric.com \
--to=alexs@ecoscentric.com \
--cc=ecos-discuss@ecos.sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).