From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Build failure - sysstat-9.0.5
Date: Sun, 29 Nov 2009 02:56:44 -0600 [thread overview]
Message-ID: <200911290256.46333.minimod@morethan.org> (raw)
In-Reply-To: <20091129093825.5d18743c@surf>
On Sun November 29 2009, Thomas Petazzoni wrote:
> Hi Michael,
>
> Le Sat, 28 Nov 2009 19:49:42 -0600,
> "Michael S. Zick" <minimod@morethan.org> a ?crit :
>
> > This one might be fixable since the mentioned missing
> > items are supposed to be built -
>
> Thank you for all your tests.
>
> Wouldn't it be better to fill bug reports in our bug tracking system
> (http://bugs.uclibc.org) ? Mails to the list are nice, but it's harder
> to keep track of what has been solved, what hasn't been solved.
>
Better for who?
The submitter or the submittie?
Working through that bug submit form/process just drops the information
into a black hole as far as the submitter can tell.
It might be a great organizational tool at the submittie end, where
being able to tag/track e-mail reports could be a pain.
But back at the submitter side = zip, zero, nada feedback to be able
to even tell if the report went into the bit bucket somewhere -
At least by e-mail, I get feedback, even the: "you screwed the options"
helps a lot.
So if you happen to read one of these mails and feel it is a problem that
will take a long enough time to solve that it might "get lost" please
feel free to assign it a bug-report number if the bug-tracker.
Mike
> Thanks!
>
> Thomas
prev parent reply other threads:[~2009-11-29 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-29 1:49 [Buildroot] Build failure - sysstat-9.0.5 Michael S. Zick
2009-11-29 8:38 ` Thomas Petazzoni
2009-11-29 8:56 ` Michael S. Zick [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=200911290256.46333.minimod@morethan.org \
--to=minimod@morethan.org \
--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