From: Bob Brusa <bob.brusa@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] adding a package with configtool fails - new stuff
Date: Wed, 27 Mar 2013 16:57:00 -0000 [thread overview]
Message-ID: <515324DB.6060502@gmail.com> (raw)
In-Reply-To: <515301CF.703@ecoscentric.com>
Am 27.03.2013 15:27, schrieb Alex Schuilenburg:
> Hi Bob,
>
> On 2013-03-27 14:03, Bob Brusa wrote:
>> [...]
>> Alex,
>> when I click on "My Bugs" I get a list of my old reports - but the bug
>> 1001798 I handed in recently is not listed. However, when searching
>> for 1001798, it is listed - and it correctly lists may name as the one
>> who reported this bug. Seems weird to me.
>
> Not weird at all. On bugs.ecos.sourceware.org "My Bugs" only lists open
> bugs, and 1001798 is resolved.
>
> If you select "My Bugs" followed by "Edit search" at the bottom of the
> search result, unselect "---" from "Resolution" and search again, you
> will get a list of all the bugs you reported or that have been assigned
> to you. You can then "Remember" the search by entering a description
> (e.g. "My Open and Closed Bugs") in the field next to "Remember search
> as" and pressing "Remember search", you will get a new link "My Open and
> Closed Bugs" at the bottom of the bugzilla page.
>
> HTH
> -- Alex
>
>
Hi Alex,
yes it helped. Thank you. Now I have a new search tab "all" which does
exactly what I would have expected from "My Bugs" as default....
Regards - Bob
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2013-03-27 16: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
2013-03-27 14:03 ` Bob Brusa
2013-03-27 14:27 ` Alex Schuilenburg
2013-03-27 16:57 ` Bob Brusa [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=515324DB.6060502@gmail.com \
--to=bob.brusa@gmail.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).