Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] preferred procedure to get new packages included
Date: Wed, 14 Jan 2009 12:33:40 +0100	[thread overview]
Message-ID: <87zlhuazqj.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1231932008.6465.7.camel@sven> (Sven Neumann's message of "Wed\, 14 Jan 2009 12\:20\:08 +0100")

>>>>> "Sven" == Sven Neumann <s.neumann@phase-zero.de> writes:

Hi,

 Sven> I am new to this list and also quite new to buildroot and I
 Sven> wonder what's the preferred procedure to get new packages
 Sven> included and packages updated. I have filed bug reports at
 Sven> bugs.busybox.net [1], but noticed that the bug-tracker does not
 Sven> send out notification emails by default.  Should I also notify
 Sven> you on this list or will bug reports be dealed with at some
 Sven> point without further action?

I've seen your patch, but haven't had time for a closer review yet.
We're trying to stabilize the tree and get a release out by February,
so it won't get committed until then.

Personally I prefer to see patches on the list, as that's easier for
reviewing, but the bugtracker is good for not forgetting about an
issue as well.

I'll look into getting bugtracker mails sent to the list as well.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-01-14 11:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 11:20 [Buildroot] preferred procedure to get new packages included Sven Neumann
2009-01-14 11:33 ` Peter Korsgaard [this message]
2009-01-15 14:07   ` Sven Neumann
2009-01-15 14:14     ` Peter Korsgaard
2009-01-15 21:08     ` Ulf Samuelsson
2009-01-16  9:37       ` Sven Neumann

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=87zlhuazqj.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.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