Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Lykowski <dan.lykowski@dynonavionics.com>
To: buildroot@busybox.net
Subject: [Buildroot] List not receiving bug reports anymore ?
Date: Mon, 15 Dec 2008 15:30:44 -0800	[thread overview]
Message-ID: <4946E8A4.2070601@dynonavionics.com> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE1909ED57CE@mi8nycmail19.Mi8.com>

hartleys wrote:
> On Monday, December 15, 2008 3:46 PM, Thomas Petazzoni wrote:
>   
>> Since November, 21st, I haven't seen a mail coming from
>> Buildroot's bug tracking system. Is it because :
>>
>> * of a technical issue ?
>> * people got fed up of filling bug reports that remained
>>   unanswered ?
>> * Buildroot is bug-free ?
>>     
>
> Probably not because of the last reason ;-)
>
> Possibly people are just posting to this list and not filing a bug
> report. I personally did not realize there was a bug tracking system.
>
> Just me two cents...
>
> Hartley
>   
It might be because the Bug Tracking link on the Buildroot site links to 
a page that says:

Bug tracker site down
The bug tracker is down while we switch from mantis to bugzilla.
Thanks!

Or maybe I am not looking in the right place for it?

Dan Lykowski
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
>   

  reply	other threads:[~2008-12-15 23:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15 22:45 [Buildroot] List not receiving bug reports anymore ? Thomas Petazzoni
2008-12-15 22:51 ` hartleys
2008-12-15 23:30   ` Dan Lykowski [this message]
2008-12-16  9:19 ` Peter Korsgaard
2008-12-16 12:22   ` Bernhard Reutner-Fischer
     [not found]     ` <87myewb501.fsf@macbook.be.48ers.dk>
2008-12-16 14:04       ` Bernhard Reutner-Fischer

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=4946E8A4.2070601@dynonavionics.com \
    --to=dan.lykowski@dynonavionics.com \
    --cc=buildroot@busybox.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