Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] contributions to buildroot...
Date: Sun, 26 Apr 2009 22:05:17 +0200	[thread overview]
Message-ID: <877i17kwoy.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <49F46C31.6050005@unix-beratung.de> (Robert Urban's message of "Sun\, 26 Apr 2009 16\:14\:09 +0200")

>>>>> "Robert" == Robert Urban <urban@unix-beratung.de> writes:

Hi,

 Robert> a while ago (15th of March) I submitted a new package,
 Robert> "ndyndns-1.14" via the mailing list.  It doesn't seem to have
 Robert> made it into the repository.

No, I've been on holiday and have quite a mail backlog..

 Robert> I don't personally care whether it ever makes it into the
 Robert> repo. I've can always add it to the stuff I check out.  I do
 Robert> however wonder why it didn't make it in.  I understand that
 Robert> you guys probably have more on your lists than you can ever
 Robert> hope to accomplish.  I appreciate your effort very much.  I
 Robert> would be helpful to me to know whether my submission was
 Robert> rejected, and why, or whether it's simply fallen by the
 Robert> wayside, which, as I said, is also ok.

I just had a look at your mail, and noticed that you just sent an URL
to an external tarball. Could you please attach the patch directly in
a mail to the list or add it to the bugtracker (bugs.buildroot.net),
then I'll review it this coming week.

 Robert> I submitted it because somewhere you guys have an exhortation
 Robert> to make packages available to others...

Not quite, the GPL says that you have to make sources available
whenever you distribute binaries - But contributing your changes to us
is ofcourse preferred.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2009-04-26 20:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-26 14:14 [Buildroot] contributions to buildroot Robert Urban
2009-04-26 20:05 ` Peter Korsgaard [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=877i17kwoy.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